feat(backend)!: pagination, geometries #9
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
Closed
zameji
force-pushed
the
feat(backend)!--pagination,-geometries
branch
from
b67ff30
to
fe6141e
Compare
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.
A small frontend change is necessary since the data format changed.
If the frontend can't be changed spontaneously, or current backend needs to be supported for a while for third party use, I can put the new backend on
/v2/intersectionand let the calls to/intersectionreturn the existing format. In that way, you wouldn't need to deploy the frontend change.@loganwilliams let me know if that's necessary