Closed Sacharified closed 2 years ago
thanks @Sacharified!
Couple of things:
Let me know what you think of those suggestions.
moving the search radius input to be inline with that label
@tomoakley Do you mean moving it out of the postcode search and in to the list component?
Agreed about the default, I'll update that.
moving the search radius input to be inline with that label
@tomoakley Do you mean moving it out of the postcode search and in to the list component?
Agreed about the default, I'll update that.
I was thinking as I typed there. Not sure it's a good idea, but I think it'd be useful to not be able to input a search radius when seeing all the results (i.e no postcode, no geo)
moving the search radius input to be inline with that label
@tomoakley Do you mean moving it out of the postcode search and in to the list component? Agreed about the default, I'll update that.
I was thinking as I typed there. Not sure it's a good idea, but I think it'd be useful to not be able to input a search radius when seeing all the results (i.e no postcode, no geo)
Yeah that makes sense.
So I could either hide it, disable it or automatically switch to Geo mode when it's typed into. Do you have any preference?
Fixes #33
This adds a search radius input, which accepts a number in Km and triggers a search with a new
radius
query parameter.The lambda now accepts a
radius
query parameter.The default radius is infinity because that's the default in the
sphere-knn
package and results in the same behaviour as what's running in prod right now.