Fix examples #575
Merged
Fix examples #575
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
Signed-off-by: Tom <[email protected]>
Signed-off-by: Tom <[email protected]>
josee-sabourin
approved these changes
Dec 11, 2023
richfab
added a commit
that referenced
this pull request
Dec 12, 2023
* Fix json * Fix examples to make them conform to json/GBFS specification * Update version in examples * Internationalization of free-form text --------- Signed-off-by: Tom <[email protected]> Co-authored-by: Tom <[email protected]>
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.
Transferring #574 to MobilityData repo to fix more typos in the examples.
What is the proposal?
Fix the examples to makes them valid JSON and conform to the GBFS specification.
Is this a breaking change?
Which files are affected by this change?
Only the examples.