Skip to content

Feature/mu ed error handling#15

Open
m-messer wants to merge 14 commits into
mainfrom
feature/muEd-error-handling
Open

Feature/mu ed error handling#15
m-messer wants to merge 14 commits into
mainfrom
feature/muEd-error-handling

Conversation

@m-messer
Copy link
Copy Markdown
Member

@m-messer m-messer commented May 8, 2026

Requires #13 and #14 to be merged to the main first.

This PR extends the previous implementation by adding the correct error handling.

m-messer and others added 14 commits May 6, 2026 11:01
…oints with authentication and runtime integration, along with associated tests
…aluate/health` paths across server and lambda integrations
# Conflicts:
#	.github/workflows/build.yml
…ndpoints with header validation, default version handling, and capability reporting
…ardize JSON responses with `writeMuEdError` and included `X-Api-Version` header validation and degraded health status support.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Relocates the spec from api/ into runtime/schema/ alongside the existing
JSON schema files, and renames it to mued_v0.1.0.yml to make the version
explicit. Removes the api/ package; embed is now owned by runtime/schema.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Previously, responses that failed spec validation were only logged as
warnings and forwarded anyway. Now a failed µEd response validation
returns 500 to the caller. The legacy / route is unaffected — it has
no matching path in the spec so the middleware passes it through
unchanged.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Resolves conflicts by keeping X-Api-Version header handling and versioning
logic from HEAD, OpenAPI middleware from incoming, and 'Evaluate' naming
throughout (MuEdBuildLegacyEvaluateRequest, MuEdToEvaluateFeedback,
NewMuEdEvaluateHealthRoute).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants