refactor: improve validation of Resource filter input
Regaez opened this issue · 1 comments
Regaez commented
The app pulls a string array from the plugin config, which is editable by the user. This could therefore be malformed and not what is expected. This should be validated first and any unsuitable values should be discarded.
Should the whole filter be discarded, or just the "incorrect" values? Leaning towards retaining a partial filter, rather than returning all Resource attributes if only one filter field is incorrect.