fix: add missing v-prefix to schema URL versions - #487
Open
nirmalnr wants to merge 1 commit into
Open
Conversation
A number of schema.nfh.global references across devkits, examples, docs, and the schema specification itself dropped the "v" prefix on the version segment (e.g. SettlementTerm/2.0 instead of SettlementTerm/v2.0) - inconsistent with the v-prefixed folder convention this repo already uses 100% of the time on disk, and often inconsistent with correctly v-prefixed refs to the same schema sitting right next to them in the same file/array. 656 occurrences fixed across 164 files (devkits, examples, docs, specification/schema). No content, structure, or non-URL text changed.
This was referenced Aug 21, 2026
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.
Summary
schema.nfh.globalreferences acrossdevkits/,examples/,docs/, andspecification/schema/itself dropped thevprefix on the version segment (e.g.SettlementTerm/2.0instead ofSettlementTerm/v2.0).v-prefixed folder convention this repo already uses 100% of the time on disk, and in several cases inconsistent with correctlyv-prefixed refs to the same schema sitting right next to the broken one in the same file/array (e.g. a Postman collection'sschemaContextarray mixingDemandFlexBuyOffer/v2.0andSettlementTerm/2.0side by side).v.Test plan
schema.nfh.global— no unrelated content touchedspecification/schema/openadr/v3.1.0/README.md— the fixed URL now matches the actualopenadr/v3.1.0folder on disk🤖 Generated with Claude Code