We currently support a single hardcoded location for the first use-case. We need to make this configurable, but also allow for multiple locations. It sounds simple enough, but there are a number of follow-on questions that will affect the design of this:
Who can change a member's location and how?
Should a member provide a location when checking in?
Should there be a list of predefined locations or should we take GPS coordinates or member-defined locations?
The output of this ticket should be an ADR that defines how we are going to handle locations going forward, with feedback from the communnity.
We currently support a single hardcoded location for the first use-case. We need to make this configurable, but also allow for multiple locations. It sounds simple enough, but there are a number of follow-on questions that will affect the design of this:
The output of this ticket should be an ADR that defines how we are going to handle locations going forward, with feedback from the communnity.