Repository navigation
fix(api): support module sort order updates - #9958
faizansaiyed123 wants to merge 1 commit into
Conversation
667f588 to
4f5a2de
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe module update serializer now accepts ChangesModule sort-order updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to This enables module sort-order updates while preserving existing creation and listing behavior. No actionable merge-blocking risk is evident. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Related to #9023.
sort_orderin the public module PATCH request.sort_orderis update-only.modules-lite?order_by=sort_order.Validation
The contract tests are designed against the existing module ordering contract and the existing
sort_orderFloatField.The MCP request model currently comes from the separately versioned
plane-sdk; enabling the MCP surface requires the corresponding SDK model update as a coordinated follow-up rather than silently accepting and dropping the field.Summary by CodeRabbit