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.

Sign up for GitHub

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

Jump to bottom

If we generate a non empty tasks.json it should not trigger intelisense #3306

Closed
isidorn opened this issue Feb 23, 2016 · 2 comments
Closed

If we generate a non empty tasks.json it should not trigger intelisense #3306

isidorn opened this issue Feb 23, 2016 · 2 comments
Assignees
@isidorn
Labels
bug Issue identified by VS Code Team member as probable bug tasks Task system issues verified Verification succeeded
Milestone
March 2016

Comments

@isidorn
Copy link
Contributor

isidorn commented Feb 23, 2016

#3159

  1. vscode workspace, delete tasks.json
  2. command > configure tasks runner
  3. a non empty tasks.json gets generated and we still trigger intelli-sense in some weird location
  4. I would expect intelli-sense is not triggered in this scenario
@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug tasks Task system issues labels Feb 23, 2016
@joaomoreno
Copy link
Member

This is on purpose, related to #3305

@dbaeumer dbaeumer added this to the March 2016 milestone Mar 1, 2016
@dbaeumer dbaeumer assigned isidorn and unassigned dbaeumer Mar 21, 2016
@dbaeumer
Copy link
Member

@isidorn the snippet story got replaced with the template story. Please verify that the new story is OK in this regard.

@isidorn isidorn added the verified Verification succeeded label Mar 23, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@isidorn isidorn

Labels
bug Issue identified by VS Code Team member as probable bug tasks Task system issues verified Verification succeeded
Projects
None yet
Milestone
March 2016
Development

No branches or pull requests
3 participants
@joaomoreno @isidorn @dbaeumer