spec: a report column of a multilingual entity is read in the caller's language - #24
Open
delchev wants to merge 1 commit into
Open
spec: a report column of a multilingual entity is read in the caller's language#24delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
…s language Mirrors intent-specification#25 into the rendered chapter: a report column bound to a translatable property is served in the caller's requested language, while what a report MATCHES stays on the stored values - so translating content never changes which rows a report returns. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirrors intent-specification#25 into the rendered site.
The Multilingual data chapter already said every read of a translatable property is served in the caller's requested language, but never said whether a report column counts as such a read — and in practice it did not, so a report grouping by a multilingual nomenclature showed the stored term right beside a list page showing the translated one, for the same record.
Changes:
docs/spec/data.md(Multilingual data → Data) — a paragraph stating that a report reads the same data in the same language, plus a::: info Normativecontainer carrying the rule and its boundary: what a report matches is unaffected, because itsfilter:, itsscope:and any condition applied to it are evaluated against the stored, untranslated values.docs/reference.md— themultilingual/languagesindex row now says the overlay applies to entity reads and report columns alike.No new construct — this constrains what a conforming generator does with the existing
multilingual:attribute. Links reuse the anchors already used elsewhere in the same chapter (/spec/presentation#reports,/spec/presentation#lifecycle-scope).