fix: api docs by clarifying file extension requirements in API paths#242
fix: api docs by clarifying file extension requirements in API paths#242auniverseaway merged 3 commits intomainfrom
Conversation
|
The integration test failure seems due to stale data in the CI test environment (3 config entries instead of expected 2). This is unrelated to the documentation changes in this PR, which only modify OpenAPI YAML files and don't affect API behavior. A CI environment cleanup or test re-run should resolve this. |
|
@kmurugulla if you would have told me you were going to do this, I would have said to update the docs in the correct location. :-) Thanks for doing this. |
|
Oh, one other thing: you'll need to build locally and commit the output. I don't believe our docs update on commit. |
@auniverseaway - could you please let me know the correct location ? |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
🎉 This PR is included in version 1.1.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
In DA admin api docs clarified file extension requirements in API paths
Related Issue
Motivation and Context
AI coding agents were not actually interpreting the API docs
How Has This Been Tested?
npm run build:docsafter modificationScreenshots (if appropriate):
Types of changes
Checklist:
Note - Please review the new docs
index.html