Fix extra space in fragment

[Trombach]

Changes

• closes Fragments are compiled with a space, which fails in TypeScript 5.7 #1053
• issue was caused by a line break token immediately before the fragment (repro), which caused hasLeadingSpace to be true
• removing the - 1 in line 709 fixes the issue, however I could not find any reason why it was subtracting 1 in the first place. Possible I've missed something
• doing this doesn't seem to break any other test cases, but fixes the problem

Testing

• added test case to check that fragments are printed properly if they are preceded by a line break

Docs

bug fix only

[changeset-bot]

🦋 Changeset detected

Latest commit: ab31d4c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@astrojs/compiler	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ematipico]

@Trombach

This is PR related to -1 https://github.com/withastro/compiler/pull/783/files

[ematipico]

If all tests pass, I believe we didn't break existing code. Also, please add a changeset to track the bug fix :)

[Trombach]

@ematipico I think that one just fixed a crash when endLoc was negative, but the code to set endLoc = n.Loc[0].Start + len(n.Data) - 1 has been there since the initial commit, so I don't know the reasoning for it. Here the value gets initiales to n.Loc[0].Start + len(n.Data), but I don't understand why it would need a -1 in the other line. It's very possible I'm missing something 🤷

[Trombach]

Sorry, I only saw your second message after I wrote my response :) I've added a changeset, hope the wording is acceptable

[ematipico]

All tests pass, so I believe your fix is correct. Worst case scenario can revert it, so it's not a huge deal. Thank you for taking the time to fix the problem