rego-evidence-report had a browser editor for Markdown policies. It shows how each line is read, as you type, and you can edit the compiled object and see the change written back into the prose.
It's useful for more than Markdown, though. Plain ergo policies, with requirements written in Rego or YAML, could get the same treatment: see each check as ergo will report it, and catch unknown operators or missing fields while you type.
It could come back as packages/editor. The Markdown side builds on packages/markdown from #18 and needs the browser entry point (web.ts) that #18 left out.
rego-evidence-report had a browser editor for Markdown policies. It shows how each line is read, as you type, and you can edit the compiled object and see the change written back into the prose.
It's useful for more than Markdown, though. Plain ergo policies, with requirements written in Rego or YAML, could get the same treatment: see each check as ergo will report it, and catch unknown operators or missing fields while you type.
It could come back as
packages/editor. The Markdown side builds onpackages/markdownfrom #18 and needs the browser entry point (web.ts) that #18 left out.