Skip to content
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

Problem Matcher support for IDF Build, Flash, and other tasks (VSC-227) #25

Closed
holubcsongor opened this issue Jan 24, 2020 · 5 comments · Fixed by #86
Closed

Problem Matcher support for IDF Build, Flash, and other tasks (VSC-227) #25

holubcsongor opened this issue Jan 24, 2020 · 5 comments · Fixed by #86
Labels
stale Stale PR or Issue

Comments

@holubcsongor
Copy link

Hello!

My problem is, that with even the 0.1.3 the VSCode can't highlight me in the Editor (or at the Problems) the errors/warnings given by the output (at build). I tried more settings in the tasks.json file, but none of it worked.
Can you give me tips to use it properly?
(I added errors to my code, it fails to build, but the VSCode doesn't recognize it as a problem.
The problem matcher pattern is matched by the output (as I tested in an online tester). )

@github-actions github-actions bot changed the title Error parser Error parser (VSC-227) Jan 24, 2020
@pwmb pwmb added the enhancement New feature or request label Jan 25, 2020
@pwmb
Copy link
Contributor

pwmb commented Jan 25, 2020

HI @bitmakk

The problem-matcher for IDF Build, flash and other such task is still under development and will be shipped soon in the upcoming versions of extension.

Update:
Adding this feature will take a while, meanwhile you could use the tasks available in task.json or write your own

@pwmb pwmb changed the title Error parser (VSC-227) Problem Matcher support for IDF Build, Flash, and other tasks (VSC-227) Jan 25, 2020
@pwmb pwmb self-assigned this Jan 25, 2020
@pwmb pwmb added this to the v0.1.4 milestone Jan 25, 2020
@holubcsongor
Copy link
Author

Thank you

@pwmb pwmb removed this from the v0.1.4 milestone Feb 14, 2020
@pwmb pwmb removed their assignment Feb 18, 2020
@brianignacio5
Copy link
Collaborator

brianignacio5 commented Feb 18, 2020

Did you try configuring your c_cpp_properties.json to use compile_commands.json ?

This is specified in C/C++ Configuration as mentioned in How to use.

As we mention in the README file, the C/C++ extension is used to resolve C headers, which is not part of our extension thereby user still need to configure it.

@pwmb pwmb added stale Stale PR or Issue and removed enhancement New feature or request labels Mar 3, 2020
@pwmb pwmb closed this as completed Mar 3, 2020
@pwmb
Copy link
Contributor

pwmb commented Mar 3, 2020

@bitmakk Adding this feature will take a while, meanwhile you could use the tasks available in task.json or write your own

@pwmb
Copy link
Contributor

pwmb commented May 18, 2020

@holubcsongor This feature request is now released and available in v0.2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale PR or Issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants