-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: refactor scope-manager config to be closer to nx OOTB #4788
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
Conversation
Thanks for the PR, @JamesHenry! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
@@ Coverage Diff @@
## main #4788 +/- ##
==========================================
- Coverage 94.27% 91.78% -2.49%
==========================================
Files 151 226 +75
Lines 8220 10548 +2328
Branches 2672 3259 +587
==========================================
+ Hits 7749 9681 +1932
- Misses 262 590 +328
- Partials 209 277 +68
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
I'm very unfamiliar with NX but reading through the docs and playing with this locally, it seems reasonable!
I'm just holding off on merging while I discuss the need for the |
Ok confirmed with Victor that this is required for now |
Refs: #4665
I was initially working through all projects simultaneously but it became clear that reviewing the ultimate PR from that would be an absolute nightmare, so I am instead going to approach it project by project (with some follow on work to then optimize once all have been largely transitioned, e.g. by pulling code from source for tests to make them faster and no longer require a full build before running)
And sorry, specifically for scope-manager we have some noise for the generated code because of changing the instructions for regenerating them. This will not be the case for other projects