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
feat(eslint-plugin): [no-circular-imports] add new rule #8965
base: main
Are you sure you want to change the base?
Conversation
Thanks for the PR, @yeonjuan! 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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
58bcfba
to
780fb1a
Compare
b64afbc
to
27d3002
Compare
PR Checklist
Overview
In this pr, I implemented
no-circular-import
which checkscircular-import
using the information thatTS
has. see #224 (comment).The current implementation lacks some handling compared to eslint-plugin-import/no-cycle. (dynamic-import, require..).
Before go any further, I have a question about the case with
dynamic-import
.With this implementation way, it would be difficult to checks for modules that reference each other via dynamic import. Actually there is a way to traverse the ASTs in the TS to check for dynamic imports, but performance may be poor.
Should this be left as an edge case?
I've already left an inquiry on discord about this. I'd be interested to hear what other members think.