conformance_and_extensions.md: add normative guidance about extension… #1682
Conversation
This file contains 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
|
I added the extension template's two issues to the OCDS 1.2 project, so I think this would now close #1571, correct? |
…lish an extension, rules about extensions, impact on validation
jpmckinney
approved these changes
Apr 4, 2024
|
those extra commits all look good, I'll go ahead and merge this |
|
@jpmckinney hmm, despite the tests passing in the PR when I merged it's created a lint error, I'm not sure how to fix that! |
|
Don’t worry, it’s a false positive |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
… paths
partially addresses #1571
The other page in this repo that references Extensions is https://standard.open-contracting.org/latest/en/guidance/map/extensions/ but all it says is of relevant here is "You can find the extension template on GitHub. It contains guidance on creating an extension." and while the guidance will be moved there will still be a link to it from the extension template so I don't think we need to alter this sentence.
This PR does not close the linked issue as it still requires updating the extension_explorer repo