-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Metadata block in Rego comment can not contain non-breaking space #4475
Comments
I have not been able to replicate this, but @anderseknert encountered this when running |
# METADATA
# description: foo is not bar
package main @johanfylling sorry, I think it's Shift + Opt + Space to create these. Not sure if GitHub is kind enough to "fix" that in the above, but if so let me know and I'll send you the file. |
I think it's fine to fail here, but the error message could certainly be improved! |
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. |
* Properly divine Rego location for yaml unmarshal errors * Error hint for cases where non-legal space is used with yaml key/value separator `:` Fixes: open-policy-agent#4475 Signed-off-by: Johan Fylling <[email protected]>
* Properly divine Rego location for yaml unmarshal errors * Error hint for cases where non-legal space is used with yaml key/value separator `:` Fixes: open-policy-agent#4475 Signed-off-by: Johan Fylling <[email protected]>
* Properly divine Rego location for yaml unmarshal errors * Error hint for cases where non-legal space is used with yaml key/value separator `:` Fixes: open-policy-agent#4475 Signed-off-by: Johan Fylling <[email protected]>
…5567) * ast: Improving error information when metadata yaml fails to compile * Properly divine Rego location for yaml unmarshal errors * Error hint for cases where non-legal space is used with yaml key/value separator `:` Fixes: #4475 Signed-off-by: Johan Fylling <[email protected]>
If the following policy contains non-breaking spaces (\u00A0)
compilation will fail with
The text was updated successfully, but these errors were encountered: