Change the API return schema for instance eco #1298
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
Previously, eco benefits were returned with a plot as an array. Mobile applications only needed to know the number of eco fields that would be included. Now, the eco fields for a plot are returned as a dictionary, so the instance API must return the keys needed to read from the dictionary and the order in which those keys should be displayed. I copied the key ordering from the current web app UI.
|
@mmcfarland @maurizi This change will most likely break the current Android application and necessitate a complimentary update. |
|
@maurizi @jwalgran - Android is still broken from the previous change to eco structure. Current issue still applies OpenTreeMap/otm-android#27 |
jwalgran
added a commit
that referenced
this pull request
Apr 14, 2014
Change the API return schema for instance eco
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.
Previously, eco benefits were returned with a plot as an array. Mobile applications only needed to know the number of eco fields that would be included. Now, the eco fields for a plot are returned as a dictionary, so the instance API must return the keys needed to read from the dictionary and the order in which those keys should be displayed. I copied the key ordering from the current web app UI.