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
The ValidationError type:
ValidationError
export class ValidationError extends Exception { public description: string; public issues?: ValidationIssue[]; constructor(description: string, issues?: ValidationIssue[]) { super(description); this.description = description; this.issues = issues; } }
contains a helpful list of validation issues, but these are not visible when an unexpected ValidationError is encountered during development:
To find the actual issues one must set a breakpoint and inspect the issues list.
The text was updated successfully, but these errors were encountered:
Good call - this is an unnecessarily awkward DX (which validations are supposed to improve).
What do you think about logging (via console.error) the description and issues when a ValidationError is created and Orbit.debug === true?
console.error
description
issues
Orbit.debug === true
Sorry, something went wrong.
Logging is fine, but with or without logging I think the exception message itself should also incorporate the validation errors.
Successfully merging a pull request may close this issue.
The
ValidationError
type:contains a helpful list of validation issues, but these are not visible when an unexpected ValidationError is encountered during development:
To find the actual issues one must set a breakpoint and inspect the issues list.
The text was updated successfully, but these errors were encountered: