api: Return typed Mermaid validation errors - #262
Merged
Conversation
- include parser diagnostics and actionable retry steps in 400 responses - cover rejection and non-persistence through API and browser tests
- rename the public issue location to requestPath - distinguish internal surface request locations from Zod schema paths
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rejects malformed Mermaid at the native write boundary and returns machine-readable recovery details while preserving the existing
errorstring.sideshow/server.Testing:
npm test,npm run coverage,npm run test:worker,npm run typecheck,npm run lint,npm run format:check,npm run security:audit, andnpx playwright test e2e/mermaid.spec.ts.