Query params
There's this tendency to think of query params as this grab bag without constraints.
But clearly, that's not true, we have to write code that responds to them. And that code likely has patterns that can be observed and extracted out.
I think there's a lot of different constraints that can be identified, e.g. a first pass:
- A query param that's free text, it can have any value.
- A query param with a fix domain of values.
- A relationship between query params, where one exists in the context of another (e.g. x=0&y=0&z=0)
- A relationship between particular routes and particular query params. E.g. some params only make sense for some url's.
It's hard to model any of this reliably without custom code. But I'm going to leave this issue open for a while to see if any good solutions/interfaces come up.