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

Disabling linting in the first folder of a multi-root workspaces disables all linters in all folders #862

Closed
DonJayamanne opened this issue Feb 22, 2018 · 0 comments · Fixed by #868
Assignees
Labels
area-linting bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@DonJayamanne
Copy link

DonJayamanne commented Feb 22, 2018

Create a multi-root setup:

  • Folder1 - Disable linting and point to a python environment without pylint
  • Folder2 - Enable linting and point to another python environment without pylint
  • Open a file in folder 2 and start editing a Python file
  • Prompt to install pylint is not dispalyed (bug)
  • Now enable linting in Folder1
  • Go back and edit the file in folder 2,
  • Prompt to install pylint is now dispalyed

Looks like we're using the wrong flags in multi-root environment for linting.

Problem

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug area-linting needs PR labels Feb 22, 2018
@DonJayamanne DonJayamanne added this to the February 2018 milestone Feb 22, 2018
@DonJayamanne DonJayamanne changed the title Linting in multi-root workspaces is broken Disabling linting in the first folder of a multi-root workspaces disables all linters in all folders Feb 22, 2018
@DonJayamanne DonJayamanne self-assigned this Feb 22, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-linting bug Issue identified by VS Code Team member as probable bug
Projects
None yet
2 participants