Fix: Add resource-specific XML examples for each endpoint #2
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.
Summary
Fixes the issue where all endpoints displayed the same generic XML examples (UsagePoint/IntervalBlock) regardless of the actual resource type being accessed.
Changes
New Resource-Specific Response Files (18 files)
Created dedicated response files for each resource type:
New Examples (previously had none):
Extracted to Standalone Files:
Inline Examples:
Path Files Updated (24 files)
Every non-Batch path file now references its resource-specific response file:
Preserved Generic Responses
AtomFeed.yamlandAtomEntry.yamlremain intactExample Conventions
All new examples follow Green Button standards:
data.greenbuttonconnect.orghttp://www.w3.org/2005/Atomhttp://naesb.org/espirel=href=type=Validation
✅
npm test- Passes with zero errors✅
npm run build- Successfully generates documentation (1007 KiB)Files Changed
Total: 44 files changed, 875 insertions, 24 deletions
Testing
After merge, verify at https://greenbuttonalliance.github.io/openapi-starter/ that:
Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com