Fix visualConfiguration schema identities - #634
Open
GenericTSDeveloper wants to merge 1 commit into
Open
Conversation
GenericTSDeveloper
force-pushed
the
junp-microsoft-fix-schema-version-mismatch
branch
2 times, most recently
from
September 1, 2026 21:56
c6a6446 to
1af2ec6
Compare
GenericTSDeveloper
changed the title
The schema published from visualConfiguration/2.0.0 advertises the 2.1.0 URL in both its \ and properties.\.const. Update those two self-identifying values to match the 2.0.0 publication path. Keep the formattingObjectDefinitions 1.4.0 and semanticQuery 1.3.0 references introduced by PR microsoft#371; those dependency upgrades were intentional. The visualConfiguration/1.8.0 embedded schema claims the \ of its sibling schema.json. Point it at its own schema-embedded.json publication path so the two different schemas no longer share one identity. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
GenericTSDeveloper
force-pushed
the
junp-microsoft-fix-schema-version-mismatch
branch
from
September 1, 2026 22:00
1af2ec6 to
5e9441e
Compare
GenericTSDeveloper
changed the title
GenericTSDeveloper
marked this pull request as ready for review
September 1, 2026 22:02
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.
Problem
Two visual configuration schemas advertise identities that do not match the files from which they are published:
visualConfiguration/2.0.0/schema.jsonadvertises the2.1.0URL in both its$idandproperties.$schema.const.visualConfiguration/1.8.0/schema-embedded.jsonclaims the$idof its siblingschema.json, so two different schemas share one identity.Fix
2.0.0/schema.jsonfrom2.1.0to2.0.0.$idto its ownschema-embedded.jsonpublication path.The dependency upgrades introduced deliberately in PR #371 remain unchanged:
formattingObjectDefinitions/1.4.0semanticQuery/1.3.0Validation
formattingObjectDefinitionsreferences remain on1.4.0semanticQueryreferences remain on1.3.0