Repository navigation
Support basepath, REST routes and errors without HTTP status - #20
Merged
Merged
Conversation
ridlfmt failed with "unknown section" on valid RIDL:
- `basepath = /v1`, an existing webrpc schema directive
- `path = /users` and `GET /{userId}` route lines, from the new webrpc
REST routes support
- `error 200 UserNotFound "user not found"` without `HTTP <status>`,
which webrpc defaults to 400
Format basepath like name/version, the service path at 2 spaces and
route lines at 6 spaces under their method. Errors without an HTTP
status keep omitting it instead of inventing one.
david-littlefarmer
approved these changes
Sep 29, 2026
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
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.
ridlfmt fails with
unknown sectionon valid RIDL, including webrpc's own_examples/golang-basics/example.ridl:basepath = /v1— existing schema directivepath = /usersandGET /{userId}— REST routes coming in webrpcerror 200 UserNotFound "user not found"— noHTTP <status>, webrpc defaults it to 400Changes:
basepathformats likename/versionpath =at 2 spaces, route lines at 6 spaces under their methodTested: the webrpc repo's
test.ridlandexample.ridlnow format, and a second run is a no-op.🤖 This message was generated by Claude on behalf of Vojtech.