test(isolated-declarations): fix multiline comment mismatch in windows

[Dunqing]

Fixes https://github.com/oxc-project/oxc/actions/runs/15327109307/job/43124348533

I don't know why it failed in Windows, I just follow the Boshen way to solve the problem.

[Dunqing]

• test(isolated-declarations): fix multiline comment mismatch in windows #11373 👈 (View in Graphite)
• 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

• May 29, 3:24 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• May 29, 3:29 PM UTC: Boshen added this pull request to the Graphite merge queue.
• May 29, 3:35 PM UTC: Merged by the Graphite merge queue.

[Copilot]

Pull Request Overview

This PR addresses inconsistent multiline JSDoc comments on Windows by converting them into single-line comments and updating the corresponding snapshot.

• Convert multiline block comments to single-line /** ... */ in fixture
• Update snapshot file to reflect the new single-line formatting

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
crates/oxc_isolated_declarations/tests/snapshots/class-decorator.snap	Updated snapshot comments to single-line format
crates/oxc_isolated_declarations/tests/fixtures/class-decorator.ts	Converted multiline JSDoc comments to single-line

[Sysix]

I don't know why it failed in Windows, I just follow the Boshen way to solve the problem.

@Dunqing In oxlint we have one test excluded in windows because of the span offset for line breaks \r\n vs \n

oxc/apps/oxlint/src/output_formatter/mod.rs

Lines 142 to 151 in 1cd8b9c

	/// disabled for windows
	/// json will output the offset which will be different for windows
	/// when there are multiple lines (`\r\n` vs `\n`)
	#[cfg(all(test, not(target_os = "windows")))]
	#[test]
	fn test_output_formatter_diagnostic_json() {
	let args = &["--format=json", "test.js"];
	Tester::new().with_cwd(TEST_CWD.into()).test_and_snapshot(args);
	}

I guess this is something similar

[Dunqing]

@Dunqing In oxlint we have one test excluded in windows because of the span offset for line breaks \r\n vs \n

oxc/apps/oxlint/src/output_formatter/mod.rs

Lines 142 to 151 in 1cd8b9c

	/// disabled for windows
	/// json will output the offset which will be different for windows
	/// when there are multiple lines (`\r\n` vs `\n`)
	#[cfg(all(test, not(target_os = "windows")))]
	#[test]
	fn test_output_formatter_diagnostic_json() {
	let args = &["--format=json", "test.js"];
	Tester::new().with_cwd(TEST_CWD.into()).test_and_snapshot(args);
	}

I guess this is something similar

Thanks for pointing it out! I will take a look.