-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
How to set exception rules for "file doesn't belong to any project" linting errors #429
Comments
This is on purpose. Nrwl/Nx is strongly opinionated, that's the point. |
Is it really? We are using semantic ui, for multiple apps. Rather than creating the same css and js files for each app, we are putting those files in libs. Libs is a natural choice for shared code. If nx makes this a hard rule, then maybe I need to manually create an assets folder or such outside of apps and libs... |
I think this should be covered by a specific "core" (or "shared") library. From my perspective, |
FYI :
|
@noelmace thanks for pointing out the changes. It turned out I just needed to add an entry into the .angular-cli.json. I'll close this issue now. |
This removes linting errors and promotes using library projects as way of sharing common features. See nrwl/nx#429 - move shared assets into single library project - update application references Thanks!
This removes linting errors and promotes using library projects as way of sharing common features. See nrwl/nx#429 - move shared assets into single library project - update application references Thanks!
If I have a directory to group libs but the directory isn't itself a lib, I get this error by having a readme in the directory.
|
@willyboy Yeah, me too. I put a README.md file in my libs/angular to introduce the different libraries inside this folder. I guess I'll delete it for now. |
@willyboy @patrick-entinux I ran into this issue today as well but I solved it by adding a The docs say:
Hope this solves your issues. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
We just upgraded from 0.9.0 to 0.11.1.
We have some static css and js files sitting in libs. When running npm run lint, we are getting these errors:
Is there a way to ignore checking certain files?
The text was updated successfully, but these errors were encountered: