feat: support lyric extension endpoints in mx::api - #394
Merged
Conversation
Preserve legacy bare lyric extensions while exposing start, continue, and stop endpoints for typed word extensions, including textless terminating lyrics.
webern
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Human Summary
Support MusicXML
start,continue, andstopextension types in API, including textless terminating lyrics.Summary
Adds typed lyric word-extension endpoints to
mx::apiwhile preserving legacy bare<extend/>behavior. The reader and writer now support text-bearing starts, intermediate continuations, and textless terminating lyrics.Testing
make api-test MX_RUNNING_IN_DOCKER=1(5965 assertions in 535 test cases)clang-format --dry-run --WerrorReferences