Follow up for #1498674: Refactor node properties to multilingual
Postponed on
Problem/Motivation
Some use cases do not support multilingual scenarios yet, as they would require a contextual information about the language to act on. Solving this was out of the scope of #1498674: Refactor node properties to multilingual and should be done after performing the conversion to EFQ2 [#X], exploiting the upcoming #1810370: Entity Translation API improvements.
In the previous issue, 1498674, in many cases contextual information about the language to filter on would have been needed, but such information is not available yet, so the queries were just adapted to use the entity language.
Proposed resolution
Add contextual information about languages in queries.
Remaining tasks
- list one example query
- identify and list all queries
- convert them (in a meta?)
User interface changes
None.
API changes
TBD
Original report in issue summary of 1498674
Contextual information: some use cases do not support multilingual scenarios yet, as they would require a contextual information about the language to act on. Solving this is out of the scope of this issue and should be done when performing the conversion to EFQ2 exploiting the upcoming #1810370: Entity Translation API improvements.