As a user, I want to get an error 400 and relevant suggestions when the properties I am using in the q and fields do not exist in the registry

[tloubrieu-jpl]

Checked for duplicates

No - I haven't checked

🧑‍🔬 User Persona(s)

Data User

💪 Motivation

...so that I can quickly identify my errors and correct them.

📖 Additional Details

No response

Acceptance Criteria

Given
When I perform
Then I expect

⚙️ Engineering Details

No response

[al-niessner]

@tloubrieu-jpl

This would require know what fields in the q, probably mostly knowable, then checking them against all known and generating errors. Do you really want this level of overhead for every check? The problem is that when you get 0 hits you do not know nor can you tell if the field does not exist but should, does not exist and should not, does exist but does not match criteria. The only of those three that a query to the registry table answers is does not exist and should not. Hence every q would have to be checked to see if the field names were bogus (as in typos or something where they do not exist because they should not exist).

What happens in an or and the user does not care about the typo it is really the other valid field they do care about? In other words, the user would be annoyed at best with 400 error because they know and do not care.