Currently, the code for determining the region of a hackathon is located in the front-end repo. Let's move this to the backend.
The Airtable contained an apac boolean, which was also migrated over this repo as a temporary solution. The new Hackathon::Region model should phase out the use of that boolean. (At the moment it's also exposed via the API to maintain existing functionality on the front end)
Currently, the code for determining the region of a hackathon is located in the front-end repo. Let's move this to the backend.
The Airtable contained an
apacboolean, which was also migrated over this repo as a temporary solution. The newHackathon::Regionmodel should phase out the use of that boolean. (At the moment it's also exposed via the API to maintain existing functionality on the front end)