Skip to content

fix(schematics): add appRoot.path for filesystem reads/writes to run linter from any directory#341

Merged
vsavkin merged 1 commit intonrwl:masterfrom
skydever:fix_project_path
Mar 25, 2018
Merged

fix(schematics): add appRoot.path for filesystem reads/writes to run linter from any directory#341
vsavkin merged 1 commit intonrwl:masterfrom
skydever:fix_project_path

Conversation

@skydever
Copy link
Copy Markdown
Contributor

I am running my ide (vscode) not from the root of the nx workspace, the nx workspace is a sub-directory of the main directory I open (with vscode). This way the linter is also not running from the root directory of the nx workspace, like mentioned at 545f2ff.

There were some changes made to the nxEnforceModuleBoundariesRule that broke the behaviour of 545f2ff. The ide is not able to show the lint errors anymore, but running ng lint is. This PR should allow the ide to also show the lint errors even if the nx workspace is not the main directory.

skydever added a commit to skydever/nx-quick-fixes that referenced this pull request Mar 19, 2018
skydever added a commit to skydever/nx-quick-fixes that referenced this pull request Mar 19, 2018
@skydever skydever changed the title fix(schematics): add appRoot.path for filesystem reads/writes fix(schematics): add appRoot.path for filesystem reads/writes to run linter from any directory Mar 21, 2018
@vsavkin vsavkin merged commit 809bdd4 into nrwl:master Mar 25, 2018
@github-actions
Copy link
Copy Markdown
Contributor

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants