[NOMERGE] feat: openapi migration progress #36458
Closed
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.
🚀 OpenAPI Migration Progress
Description:
This PR tracks the ongoing progress of migrating
Rocket.Chat APIendpoints to the new OpenAPI pattern with AJV validation and improved documentation. It will be continuously updated to reflect completed and remaining work.✅ Summary
🚨 Core API Endpoints
These are 506 endpoints critical for core features and should be migrated first:
Authentication (0 / 9 completed)
Content Management (0 / 12 completed)
Integrations (2 / 13 completed)
Marketplace Apps (0 / 4 completed)
Messaging (0 / 39 completed)
Omnichannel (0 / 154 completed)
Miscellaneous (0 / 26 completed)
Notifications (0 / 6 completed)
Rooms (0 / 126 completed)
Settings (0 / 48 completed)
Statistics (0 / 16 completed)
User Management (0 / 53 completed)
Let me know if you'd like these grouped, categorized, or documented further.
📝 Secondary API Endpoints
These endpoints are lower priority and can be migrated after core APIs: (calculating...)
🧪 Testing Plan
💡 Notes
Looking forward to your feedback 🚀