Do not parse pass-through information in GBFS mappers - #3709
Merged
hannesj merged 1 commit intoNov 2, 2021
Merged
Conversation
Member
|
I'm surprised that you didn't have to touch any of the API mapping code for this. I guess these fields are simply never accessed and not exposed via any API, isn't it? |
Contributor
Author
|
Yes. They are only read, but not yet exposed through any API |
leonardehrenfried
approved these changes
Nov 1, 2021
t2gran
approved these changes
Nov 2, 2021
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
3 participants
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
Remove parsing of data in GBFS mappers, which can be presented as strings to the user.
Issue
closes #3708
Unit tests
None updated
Documentation
None needed