Double-indented text does not produce a warning

[justingrant]

From tc39/proposal-temporal#2621 (comment):

The following spec text did not produce any complaints from ecmarkup. I would have expected that only one additional level of indentation (two spaces) is allowed.

      1. Else if _parseResult_ contains a |UTCOffsetSubMinutePrecision| Parse Node, then
          1. Let _offset_ be the source text matched by the |UTCOffsetSubMinutePrecision| Parse Node contained within _parseResult_.
          1. Set _timeZoneResult_.[[OffsetString]] to CodePointsToString(_offset_).

[bakkot]

Handling of whitespace is generally managed by the formatter, not the build job, and indeed if you run the formatter on this input it will fix it for you.

[justingrant]

Oh! Got it, sorry for the spam. The spec workflow in the Temporal repo has never used the formatter, but as we get closer to Stage 4 we should start using it. Issue opened. Thanks!