The availability range is currently hard-coded, and it should be retrieved from the DB instead.
I would've resolved this in #102, but there's much more spaghetti than I could untangle. It feels like legacy code, and we haven't even entered production.
E.g., the PageLoad data is drilled all the way down, which both means that it doesn't have proper typing and that identifying downstream effects is quite difficult.
Ideally, in implementing this feature, we also fix the above problem.
The page load data should populate stores which can then be read anywhere.
At the very least, data passed down the component tree should be filtered and typed to only what is necessary.
Description
PageLoaddata is drilled all the way down, which both means that it doesn't have proper typing and that identifying downstream effects is quite difficult.