c9fc66620 introduced error reporting if the user requests to render a project field that doesn't exist, eg with api/v1/projects?field[]=no_such_field.
The refactoring to do this accidentally left the queryable attribute off the state field (and only that field!), and we had no error reporting to warn the user they were searching on unqueryable fields, so, eg, api/v1/projects?state=P3.proj_avail would silently ignore the state query term and would return all projects.
Make state work again. (Should there be a hat for this?)
Add error reporting on unrecognized query keys, eg api/v1/projects?eligible_for_bulwer_lytton=yes, which would have exposed this.
c9fc66620 introduced error reporting if the user requests to render a project field that doesn't exist, eg with
api/v1/projects?field[]=no_such_field. The refactoring to do this accidentally left the queryable attribute off thestatefield (and only that field!), and we had no error reporting to warn the user they were searching on unqueryable fields, so, eg,api/v1/projects?state=P3.proj_availwould silently ignore thestatequery term and would return all projects.statework again. (Should there be a hat for this?)api/v1/projects?eligible_for_bulwer_lytton=yes, which would have exposed this.