-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: add raw localizations to meta types, fields and enums #314
Conversation
7924603
to
ba10b81
Compare
Can be reviewed again. |
Should I also add tests in |
ah yes please, forgot about them here. You could probably also add some unit tests that query the properties in the |
ba10b81
to
65445d6
Compare
Added the tests. |
@@ -939,6 +1024,84 @@ describe('Meta schema API', () => { | |||
}); | |||
}); | |||
|
|||
it('can query raw localization of types', async () => { |
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.
maybe add a test for a field where only one of the languages is present, to make sure the value omits this key then?
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.
added a test for a field on the root entity type and a value object, both with only german translations
Currently, it is only possible to query localizations by explicitly specifying the target language for the client. There are also use-cases where the localization is not immediately used in a client, but needed to be processed in another system. In this case it is convenient to be able to query the translations in all locales in a single request.
65445d6
to
4b98144
Compare
Currently, it is only possible to query localizations by explicitly specifying the target language for the client. There are also use-cases where the localization is not immediately used in a client, but needed to be processed in another system. In this case it is convenient to be able to query the translations in all locales in a single request.