discourse-mirrors/discourse-translator
0
0
Fork 0
mirror of https://ghfast.top/https://github.com/discourse/discourse-translator.git synced 2026-07-15 11:36:26 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
discourse-translator/spec/fabricators
History
Exact
Natalie Tay 7fc45d5be8
DEV: Move translation custom fields into their own tables (#201) 
Currently, `Topic` and `Post` have detected_language and translations in custom fields, e.g.
```
post.custom_fields[DiscourseTranslator::DETECTED_LANG_CUSTOM_FIELD]
post.custom_fields[DiscourseTranslator::TRANSLATED_CUSTOM_FIELD]
topic.custom_fields[DiscourseTranslator::DETECTED_LANG_CUSTOM_FIELD]
topic.custom_fields[DiscourseTranslator::TRANSLATED_CUSTOM_FIELD]
```

We are moving this into 4 tables/models
```
post has_one :content_locale, class_name: "DiscourseTranslator::PostLocale"
post has_many :translations, class_name: "DiscourseTranslator::PostTranslation"
topic has_one :content_locale, class_name: "DiscourseTranslator::TopicLocale"
topic has_many :translations, class_name: "DiscourseTranslator::TopicTranslation"
```

Since there are a lot of duplicates, this is implemented on the `Post` and `Topic` using a `Concern`, and any future translatable content can inherit this concern.

This PR also gets rid of the previous N+1 which happens when determining if the 🌐 translate button should appear for each post.
2025-02-10 12:29:07 +08:00
..
post_locale.rb DEV: Move translation custom fields into their own tables (#201) 2025-02-10 12:29:07 +08:00
post_translation.rb DEV: Move translation custom fields into their own tables (#201) 2025-02-10 12:29:07 +08:00
topic_locale.rb DEV: Move translation custom fields into their own tables (#201) 2025-02-10 12:29:07 +08:00
topic_translation.rb DEV: Move translation custom fields into their own tables (#201) 2025-02-10 12:29:07 +08:00