chore(prettier_conformance): improve the information that is shown in filter

[Dunqing]

Shows information that would be helpful for humans and AI to debug

[Dunqing]

• fix(formatter): preserve trailing comments before the semicolon in class methods without a body #18446
• chore(formatter): support --diff in example #18443
• chore(tasks): unify printing differences for mismatch code #18441
• chore(prettier_conformance): improve the information that is shown in filter #18439 👈 (View in Graphite)
• refactor(tasks): improve terminal diff output with context lines #18437
• 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.

[Boshen]

Merge activity

• Jan 23, 8:47 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 23, 8:47 AM UTC: Boshen added this pull request to the Graphite merge queue.
• Jan 23, 8:53 AM UTC: The Graphite merge queue couldn't merge this PR because it had merge conflicts.
• Jan 23, 11:54 AM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
• Jan 23, 11:54 AM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..
• Jan 23, 11:54 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 25, 7:02 AM UTC: The merge label '0-merge' was removed. This PR will no longer be merged by the Graphite merge queue
• Jan 25, 7:02 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 25, 4:33 PM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
• Jan 25, 4:33 PM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..
• Jan 25, 4:33 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 26, 1:25 AM UTC: The merge label '0-merge' was removed. This PR will no longer be merged by the Graphite merge queue
• Jan 26, 1:25 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jan 26, 1:42 AM UTC: Dunqing added this pull request to the Graphite merge queue.
• Jan 26, 1:48 AM UTC: Merged by the Graphite merge queue.

[codspeed-hq]

Merging this PR will not alter performance

✅ 42 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing 01-23-chore_prettier_conformance_improve_the_information_that_is_shown_in_filter (6271dbb) with main (7ba9fa1)²}

Footnotes

1. 3 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. ↩

2. No successful run was found on graphite-base/18439 (7f070db) during the generation of this report, so main (7ba9fa1) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩