-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
fix(linter): disable absolute paths within project #5555
fix(linter): disable absolute paths within project #5555
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/CN9W1HU5D6WChSEkiVRdZR1Dsoqd |
Nx Cloud ReportCI ran the following commands for commit 8ccdf3e. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch
Sent with 💌 from NxCloud. |
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.
LGTM! 🎉
Can you see why the e2e tests are failing? |
Looks like a timeout. I'll look into it tomorrow. |
I think this can be a breaking change for a lot of folks. Should we have a flag that allows you to switch it off? |
Good point, @vsavkin! I will add the flag |
Hello! I can confirm that this is a breaking change, because I actually need to do this when using secondary entry point for a library. When code in the secondary entry point import something from the main entry point. @meeroslav nx/packages/eslint-plugin-nx/src/rules/enforce-module-boundaries.ts Lines 65 to 79 in 4b73b7c
Unfortunately without it, eslint is rejecting the new config with a ""Configuration for rule "@nrwl/nx/enforce-module-boundaries" is invalid" |
@Wykks Thank you for the fast feedback. The missing schema property definition was accidentally removed. I will add it asap. |
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. |
Current Behavior
If a project imports from itself using the full package name, the lint rule does not detect a circular dependency.
Expected Behavior
The linter should report an error with information why the error happened.
e.g.
Related Issue(s)
Fixes #2019