Skip to content

api: clef number attribute does not round-trip #270

Description

@webern

Split out of #230, which grouped unrelated attribute drops on different elements. One repro per issue.

What

The clef number attribute does not round-trip. Investigation (PR #267) found the divergence is the
reverse of a plain drop: for single-staff parts mx added a spurious number="1" on mid-measure
clef changes, where the source omits it (1 is implied). The classifier signature attr:clef@number
covers any mismatch in either direction.

Verified on lysuite/ly46c_Midmeasure_Clef.xml.

Impact

attr:clef@number — 29 reorder-free candidate files (the largest single attribute signature in the worklist).

Repro

make dump-api-roundtrip && make classify-api-roundtrip   # signature attr:clef@number

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    aiIssues opened by, or through, a coding agent.area/mx::apiarea/mx::implbugsoftware defect

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions