test: '@'-prefixed member names, rejected as terms and opaque inside a value - #71
Merged
Merged
Conversation
…a value Covers both halves of the rule. As an Attribute name and as a sub-attribute of a Relationship, "@referredType" and "@weird" are 400 BadRequestData and the entity is not created. Inside a value they mean nothing and must round-trip untouched: "@none" in a languageMap, '@'-keys inside a JsonProperty's json, a {"@type":"@JSON","@value":...} literal, and an '@'-key in a plain Property value object. The second half is the one that constrains a future fix: the rule is about name positions, and a broker that applied it to value positions would break LanguageProperty. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mo7DQD14mrErQD4N2v99d2
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.
Functest for #70. Depends on SEAMWARE/corJsonld#5 and SEAMWARE/corNgsild#17 — CI clones
mainof each sibling, so this stays red until both are merged.Covers both halves of the rule:
@referredType/@weirdare 400BadRequestData, and the entity is not created.@nonein a languageMap,@-keys inside a JsonProperty'sjson, a{"@type":"@json","@value":…}literal, and an@-key in a plain Property value object.The second half is the one that constrains a future fix. The rule is about name positions; a broker that applied it to value positions would break LanguageProperty.
Run twice back to back, and against the unfixed broker to confirm it fails there.
Closes #70
🤖 Generated with Claude Code
https://claude.ai/code/session_01Mo7DQD14mrErQD4N2v99d2