Skip to content

fix: problemMatcher assumes relative paths #4281 #4282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

paulkilroy
Copy link

@paulkilroy paulkilroy commented Mar 30, 2025

When you compile code in VSCode with platform IO, the first tab at the bottom ("problems") Does not correctly parse the filename and line number, changing to let the problem matcher try to guess is the paths are relative or absolute fixes this. Tested on linux and macos.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link

stale bot commented Jun 26, 2025

This issue has been automatically marked as stale because it has not had recent activity. Please provide more details or it will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 26, 2025
@paulkilroy
Copy link
Author

When you compile code in VSCode with platform IO, the first tab at the bottom ("problems") Does not correctly parse the filename and line number, changing to let the problem matcher try to guess is the paths are relative or absolute fixes this. Tested on linux and macos.

@stale stale bot removed the stale label Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants