34
Add dedicated `lang` parameter
Source: directus/directus#6654 · opened by @lluishi93
We have a project with complex json structures as a result from many nested relationships. We relied on the &lang= query param from v8 to acquire the corresponding translations, but we now see that v9 does NOT have anything similar, as far as we've seen. The only similar feature to that would be the &deep[translations][_filter][language]=es-es query param , but this makes us define the filter for every nested items, which is not what we expected when thinking about migrating to v9. Is there any feature similar to the &lang query param in v9 that we're not aware of?
If not, it'd be a nice idea to introduce it, because I assume that a lot of people will be in the same situation as us.
What we want to do
![image](
What we have to do
![image](
If not, it'd be a nice idea to introduce it, because I assume that a lot of people will be in the same situation as us.
What we want to do
![image](
What we have to do
![image](
No pledges yet. Be the first to back this.
Comments
Similar requests
Automatic Language Selection in Translations interface for Visual Editor
5 votes · 0 comments
RTL Support
5 votes · 0 comments
Dynamic filter on existing field values
1 vote · 0 comments
Allow deleting translations from translations interface
21 votes · 0 comments
Default Field Values per Language
2 votes · 0 comments
No comments yet.