-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
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
internal/core: concreteness errors not reported when conflict errors are present in other values #1319
Comments
Passing comment: we discussed the different types/categories of errors a good deal whilst considering #822. |
See also the discussion in #1998. |
I believe this issue is also present when This is a recent change, using this version of
Testscript:
Expected: passing script.
|
What version of CUE are you using (
cue version
)?0.4.0
What did you do?
I expected all errors for fields which do not interact. Instead I saw a series of errors shown depending on what other errors were found prior.
What did you expect to see?
What did you see instead?
if
s
is not presentif both
s
andv
are not presentErrors are not in the order they appear. Having them in the same order as they appear in the file would be nice. Probably a separate issue.
The text was updated successfully, but these errors were encountered: