fix(formatter): correct comments checking for some places

[Dunqing]

No description provided.

[Dunqing]

• fix(formatter): correct comments checking for some places #14153 👈 (View in Graphite)
• fix(formatter): print comments incorrectly if the node is without following a node #14110
• fix(formatter): merge the right side of LogicalExpression if it's a LogicalExpression and both have the same operator #14097
• feat(formatter): correct printing parameters with return_type for function-like node #14084
• feat(formatter): normalize key of TSPropertySignature #14083
• fix(formatter): correct printing comments within the type annotation of ArrayPattern and ObjectPattern #14077
• fix(formatter): correct printing comments around decorators #14076
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #14153 will not alter performance

_{Comparing 09-26-fix_formatter_correct_comments_checking_for_some_places (cda9e16) with main (588acd5)¹}

Summary

✅ 33 untouched
⏩ 4 skipped²

Footnotes

1. No successful run was found on main (a2914fe) during the generation of this report, so 588acd5 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩