We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Related to #520
Would actually be possible to validate the data coming from the API to prevent situations like #520 where gqty is not the one at fault?
gqty
The text was updated successfully, but these errors were encountered:
We definitely don't want to validate too much (ajv as an extreme case), that defeats the benefits of TypeScript.
ajv
I suggest minimal assertions, e.g. invariant or assert, with a message containing enough information for users to start looking at server side.
invariant
assert
invariant(data.allMfes0, "Response with alias `allMfes0` expected.");
Sorry, something went wrong.
No branches or pull requests
Would actually be possible to validate the data coming from the API to prevent situations like #520 where
gqty
is not the one at fault?The text was updated successfully, but these errors were encountered: