fix: When running a linter through WSL, the file where the error occu…

[yaoyao22fanfan]

[Unreleased]

Changed

• fix: When running a linter through WSL, the file where the error occu)rred cannot be correctly indicated #530

[Copilot]

Pull Request Overview

This PR fixes an issue where running a linter through WSL (Windows Subsystem for Linux) fails to correctly identify the file where errors occurred. The fix involves converting WSL paths to Windows format and cleaning up NUL characters from the output.

Key changes:

• Added path conversion from WSL format to Windows format for proper file identification
• Added cleanup of superfluous NUL characters from linter output
• Minor code formatting improvements

Reviewed Changes

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

File	Description
src/linter/VerilatorLinter.ts	Implements WSL path conversion and NUL character cleanup to fix file path resolution
CHANGELOG.md	Documents the bug fix in the changelog

Comments suppressed due to low confidence (1)

src/linter/VerilatorLinter.ts:68

• [nitpick] The function name 'convertFromWslPath' is ambiguous about the direction of conversion. Consider renaming to 'convertWslPathToWindows' to clearly indicate it converts from WSL format to Windows format.

  private convertFromWslPath(inputPath: string): string {

[Copilot]

The function does not handle potential errors from execSync. If the wslpath command fails, this will throw an exception without a clear error message indicating the WSL path conversion failed.

Suggested change

	return child.execSync(cmd, {}).toString().replace(/\r?\n/g, '');
	try {
	return child.execSync(cmd, {}).toString().replace(/\r?\n/g, '');
	} catch (error) {
	this.logger.error(`Failed to convert WSL path: ${inputPath}. Error: ${error.message}`);
	return inputPath; // Fallback to the original path
	}