Integrate Extension Explorer #195
Merged
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
|
Note that the mysterious milestones extension is still linked from the sidebar. We can address that separately in #194. |
|
Having repeated this process on the standard, I'm confident in this PR, so will merge once tests complete. |
|
The schema tests had become more strict, so I had to update to v1.1.4 of core extensions. |
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.
closes #193, closes #189
This uses a new directive to link to the Extension Explorer with the versions of extensions as configured in conf.py. Links use the correct language prefix for the Extension Explorer.
See screenshot, in which extension names are translated, thanks to the
extensions.jsonfile offered by the Extension Explorer and used by the directive.http://standard.open-contracting.org/profiles/ppp/extensionexplorer/es/extensions/