Skip to content
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

Add support for a base translation profile #282

Closed
4 tasks
MLenterman opened this issue Feb 27, 2024 · 0 comments · Fixed by #296
Closed
4 tasks

Add support for a base translation profile #282

MLenterman opened this issue Feb 27, 2024 · 0 comments · Fixed by #296
Assignees
Labels
feature New feature or request

Comments

@MLenterman
Copy link
Collaborator

Currently a translation profile only applies to a single zaaktype. As a result, common translation behavior and/or defaults need to be copied/pasted often for each zaaktype. We would like to have the option to add a base translation profile. With a base profile defined, the more specific per zaaktype profile should be merged on top of the base profile to obtain the final profile.

base profile zaaktype profile result profile
a: default value 1 a: default value 1
b: default value 2 b: 12345 b: 12345
c: default value 3 c: default value 3

The base profile can be just another profile in profiles.json with a '*' as zaakTypeIdentificatie.

  • Add base translation profile
  • Adapter that resolves the value for a given key from the merged base + specific translation profile
  • Implement adapter everywhere where a translation profile property is used.
  • User documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
2 participants