Authored with @egorio. We paired on this solution.

Problem

• Glint Plugin would incorrectly insert comments within an mustache statement nearest the site of the glint error.
• The diagnostic would point to the actual start of the bad argument.

{{concat
  {{! @glint-expect-error @rehearsal TODO TS2339: Property 'someArg1' does not exist on type '{}'. }}
  @someArg2
  @someArg3
  @someArg4
  @someArg5
  @someArg6
  @someArg7
  @someArg8
  @someArg9
  @someArg10
}}

This fixes #1119 and another issue where a multiline handlebars statement within an html tag would produce invalidate handlebars syntax after running migrate.

<div
  class="{{concat
       {{! @glint-expect-error @rehearsal TODO TS2339: Property 'someArg1' does not exist on type '{}'. }}
      @someArg1
      @someArg2
      @someArg3
      @someArg4
      @someArg5
      @someArg6
      @someArg7
      @someArg8
      @someArg9
      @someArg10
    }}"
>
  Hello World!
</div>

Why is this important?

When rehearsal runs against our internal products it breaks .hbs files.

Changes

• When given a diagnostic in an .hbs context, it will find up to the opening curlies, and inject there.
• DRYs up usage of change magicString changeTracker.appendRight method.

TODO

• Need to write a smoke-test for this using a angle bracket component invocation with a glint error.

<MyComponent
  @badArg
  @someArg2
  @someArg3
  @someArg4
  @someArg5
  @someArg6
  @someArg7
  @someArg8
  @someArg9
  @someArg10
}}
/>