Postcode field #1500
Merged
Postcode field #1500
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
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.
Description
We got a request to add postcode field to the location output and to be able to sort signals by that postcode.
Currently the postcode is stored inside a JSON field (
address) and inside a text field (address_text). However that situation is unfortunately not very reliable and not very optimal for things like sorting/ordering.This PR adds an optional postcode field to the location model, makes sure it can be found in the list endpoint's output and allows ordering using that field. Nothing has been changed to the
addressandaddress_textfields to remain backwards compatible.