docs: auto-generate service definition table from schema#285
Open
leoneperdigao wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
Conversation
Replace the hardcoded service definition table with the extension_schema_fields macro to keep the documentation in sync with the actual service.json schema. The previous table described an outdated nested structure (rest.schema, mcp.endpoint, etc.) that no longer matches the current flat transport-based schema. Fixes Universal-Commerce-Protocol#136
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.
Description
Replace the hardcoded service definition table in the Overview page with the
extension_schema_fieldsmacro, which auto-generates the table from the actualservice.jsonschema.The previous hardcoded table described an outdated nested structure (
rest.schema,rest.endpoint,mcp.schema,mcp.endpoint, etc.) that no longer matches the current flat transport-based schema which usestransport,schema, andendpointas top-level fields.By using the same macro approach already used for the Capability Definition table, the service definition documentation will now stay automatically in sync with any future schema changes.
Type of change
Checklist
Fixes #136