-
Notifications
You must be signed in to change notification settings - Fork 39
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
Evaluate code lens doesn't work if input.json isn't found #1294
Labels
Comments
anderseknert
added a commit
that referenced
this issue
Dec 11, 2024
Fixes #1294 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Dec 12, 2024
Fixes #1294 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Dec 12, 2024
Fixes #1294 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Dec 12, 2024
Fixes #1294 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Dec 12, 2024
Fixes #1294 Signed-off-by: Anders Eknert <anders@styra.com>
charlieegan3
pushed a commit
to charlieegan3/regal
that referenced
this issue
Jan 6, 2025
Fixes StyraInc#1294 Signed-off-by: Anders Eknert <anders@styra.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure when this happened, but at least on current main, it seems like Evaluate only works when an input.json/yaml is found. Even when a rule that doesn't depend on the input is evaluated. We should fix this before next release.
The text was updated successfully, but these errors were encountered: