fix: @W-19772910@ Fixed issue with relative paths #291
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
randi274
approved these changes
Oct 7, 2025
| const pathSepVar: string = path.sep.replaceAll('\\', '\\\\'); | ||
| const runDir: string = process.cwd().replaceAll('\\' , '\\\\'); | ||
|
|
||
| const codeAnalyzerVersion: string = (JSON.parse((await fs.promises.readFile(path.join(require.resolve('@salesforce/code-analyzer-core'), '..', '..', 'package.json'), 'utf-8'))) as any).version; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Previously, the Code Analyzer tools accepted relative paths, which could cause issues when the MCP server was running from an unexpected directory. Now the tools specify that only absolute paths should be provided.
Also bumps SFCA Core engines to latest versions.
What issues does this PR fix or reference?
@W-19772910@