Open tinatownes opened 6 months ago
There are a number of reasons that the API server doesn't currently validate request parameters, but it would not be "too hard" to do stuff client-side that checks to see that the requested values are present in the metadata... ¯\_(ツ)_/¯
Agreed, that error message is not very helpful and the source + signal names are very fragile. This should be quite doable, especially given that we already have code that parses metadata and builds a table of available source-signal pairs.
When using the epidatr API, if an incorrect value is entered in an attempt to fetch data for a signal, the only message received is:
Is it possible to have a more descriptive warning message that informs user what actual value is incorrect?
In this example, source = "fb-survey" is incorrectly written as "fb_survey", but the warning message does not specify what value is problematic:![image](https://github.com/cmu-delphi/delphi-epidata/assets/11445176/55961869-e1e6-4d3f-8095-075c31eb3184)