Feat: adds geojson support for working with the PostGIS extension #721
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
dshukertjr
reviewed
Nov 21, 2023
Co-authored-by: Tyler <[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.
What kind of change does this PR introduce?
Adds
geojsonsupport for returning PostGIS datatypesWhat is the current behavior?
Currently, geojson is not supported.
What is the new behavior?
Adds a
geojsonmethod to pass the postgis content type and tell PostgREST to respond appropriately https://postgrest.org/en/stable/how-tos/working-with-postgresql-data-types.html#ww-postgisAdditional context
Enabled the
PostGISextension for the test cases also (mentioning here for search-ability in case it introduces issues down the line)