-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: team_settings
column rename from boundary_json
to boundary_bbox
#3375
Conversation
🤖 Hasura Change Summary compared a subset of table metadata including permissions: Updated Tables (1)
|
@DafyddLlyr @jessicamcinchak I seem to be pulling in a few quotation mark changes on the .yml file, is this a prettier issue? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once this is merged I'll line up a production deploy so that the sync scripts can also be easily updated to point at the new column 👍
Removed vultr server and associated DNS entries |
@RODO94 I'm not sure if it's a prettier issue - maybe a different version of the Hasura CLI or something like that? Ideally we wouldn't commit a noisy change unnecessarily, but it doesn't make a functional difference if either |
…438) ## What does this PR do? This PR updates functions and types relating to ``team_settings`` with the new ``boundary_bbox`` column which replaces the previous ``boundary_json`` column: theopensystemslab/planx-new#3375
What does this PR do?
This PR will set up work to add a outer boundary json to the database for a local authority using the data in the
boundary_url
columnFollowing this work, when a user updates the
boundary_url
column, it will trigger a fetch to get the GeoJSON and then pass it through turf.js to turn it into aboundary_bbox
JSON. This initial migration will enable easier follow on work.