Closed Kikobeats closed 5 years ago
Because we are considering adding a microlink-api code connector (https://github.com/microlinkhq/open/issues/5) probably this kind of validation has more sense to be done on the client library instead of adding more logic into API layer and making it slower.
@Kikobeats while the validation might be better to do client side, would it be possible to have a more descriptive error message so it's easier to identify the issue?
That's true, let me identify kind of errors we are handling and create a list of well human errors message we can report
Current Behavior
If there is an error (for example a typo) in the selector of the custom rule then the server seems to crash and return a 404 not found.
Example
returns
Here's an example (notice the spelling of the word
first
in the selector has a typo):