Starting with the version of @glimmer/syntax that landed in Ember 3.25, synthetic attributes added to an element node trigger a warning because their loc is treated as a real source location at offset 0, and the content there typically won't match the name of the attribute being emitted.
Ultimately it would be great to fix that, but given that the fix is unlikely to get backported to all affected Ember versions, we're including a workaround here in the meantime.
Starting with the version of
@glimmer/syntaxthat landed in Ember 3.25, synthetic attributes added to an element node trigger a warning because theirlocis treated as a real source location at offset 0, and the content there typically won't match the name of the attribute being emitted.Ultimately it would be great to fix that, but given that the fix is unlikely to get backported to all affected Ember versions, we're including a workaround here in the meantime.