Expose system-object staves to plugins - #34882
mnorrisvuw wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe Merge Risk: ⚪ Minimal · up to This adds read-only plug-in access to configured system-object staves while preserving exclusion of the separately handled top staff. The change is ready to merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Linked repositories: Public OSS repositories can only analyze public repositories installed in this organization. No linked repositories were analyzed; skipped 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 |
Resolves: #30712
Summary
Expose
curScore.systemObjectStavesto QML plug-ins.Description
Plug-ins currently cannot directly access the staves configured by the user to display system objects.
This PR adds a read-only
systemObjectStavesproperty, returning the existing score-level list as APIStaffobjects. The list contains the additional system-object staves and excludes the top staff, which MuseScore handles separately.Validation
The following commands completed successfully:
Uncrustify version: 0.74.0. The changed API source compiled successfully; the repeat build check was up to date. A full application build and manual plug-in test have not been performed for this change. No new test was added for this basic API exposure change. No prior PR referencing #30712 was found; the issue contains an earlier request from another contributor to be assigned.
Checklist