Nicer errors on "evaluate" with syntax errors in context/entities

[john-h-kastner-aws]

The fall-through to WASM errors didn't given useful error messages. By treating an invalid context as empty we would get some unrelated validation error complaining about missing attributes, or it could even proceed to authorization if the action accepted an empty context.

For invalid JSON in the context:

old:

new:

[Copilot]

Pull request overview

Improves the Policy Playground “Evaluate” flow by surfacing a clear UI error when context or entities contain invalid JSON (instead of deferring to WASM error output), and adds regression tests covering both invalid-input cases.

Changes:

• Add explicit JSON parsing with early-return error output for entities and context in evaluateInput.
• Add sandbox tests that load invalid entities/context via URL hash and assert the improved error message is shown.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/routes/policy-playground/PolicyPlayground.tsx	Adds explicit JSON parse error handling for entities and context before invoking isAuthorized.
tests/sandbox.test.tsx	Adds tests that verify the UI displays the “Invalid context or entities input” message for invalid JSON in entities and context.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.