You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Project validation is the only component that does not have it's own error type in errors.go. The error messages are currently constructed as strings which makes it difficult to verify error types when testing the negative path.
Also, the ValidateDevfileData function returns a concatenation of error strings. We should switch to returning a multierror which was recently introduced in #577
scratch this, I didn't have the latest changes in my local repo
To Reproduce:
Expected behavior
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.
Additional context
Any workaround?
Suggestion on how to fix the bug
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
/kind bug
Which area this bug is related to?
/area library
Bug Summary
Describe the bug:
Project validation is the only component that does not have it's own error type in errors.go. The error messages are currently constructed as strings which makes it difficult to verify error types when testing the negative path.
Also, the ValidateDevfileData function returns a concatenation of error strings. We should switch to returning a multierror which was recently introduced in #577scratch this, I didn't have the latest changes in my local repo
To Reproduce:
Expected behavior
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.
Additional context
Any workaround?
Suggestion on how to fix the bug
The text was updated successfully, but these errors were encountered: