-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#3718] Drop FormDefinition.component_translations JSONField #3960
[#3718] Drop FormDefinition.component_translations JSONField #3960
Conversation
fc4d8c5
to
d6fdf43
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3960 +/- ##
==========================================
- Coverage 96.12% 96.09% -0.04%
==========================================
Files 724 724
Lines 22631 22609 -22
Branches 2610 2602 -8
==========================================
- Hits 21755 21726 -29
- Misses 621 629 +8
+ Partials 255 254 -1 ☔ View full report in Codecov by Sentry. |
d6fdf43
to
5e8f153
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a general question: I see form definition translations are removed from the frontend here. What was happening until now when component translations were set, as well as fd translations? Did one took priority over the other?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably I don't understand your point..I mean component_translations
JSONField had the translations for all the components (literals) and it was part of the form definition model. Or maybe I have missed something in the old flow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: is file src/openforms/forms/fd_translations_converter.py
still needed?
I think you are right, maybe I missed that..I will have a look again. |
25b2131
to
2d5943c
Compare
We removed the 'component_translations' field since it's deprecated. The new formiobuilder handles the translations per component. The field is still present in the FormDefinitionSerializer since we need it during import of older forms, to process legacy format component translations.
895670d
to
f32dc67
Compare
Closes #3718