-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix IntelliSense in VSCode export #9649
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
Conversation
@ngraziano, thank you for your changes. |
Thanks @ngraziano for the contribution. Our teams will review. This PR is fixing #7863 ? |
It should fix #7863 (You make me discover this issue). But when reading #7863 (comment) , I see there is other improvement that can be added to the pull request :
Do I have to complete this PR or create another one ? |
Can complete it if you have time now, while we review - adding separate commits. As these will be simple fixes |
Please target master branch |
Allow to use default intelliSenseEngine in visual studio code. Add of compilerPath and forcedInclude of mbed_config header in the created c_cpp_properties.json file.
VSCode handle "/" and it is easier to read.
Replace with ${workspaceFolder}
5e9aa47
to
e85bbdd
Compare
It should target master now. |
@janjongboom Would you be able to locally test this PR on your machine to conform the VSCode changes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix!
While we are waiting, I'll start CI |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
Allow to use default intelliSenseEngine in visual studio code.
Add of compilerPath and forcedInclude of mbed_config header in the
created c_cpp_properties.json file.
Description
Allow to use default intelliSenseEngine in visual studio code.
Add of compilerPath and forcedInclude of mbed_config header in the
created c_cpp_properties.json file.
Pull request type