-
-
Notifications
You must be signed in to change notification settings - Fork 598
Add circular dependency detection to CI #1346
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
Add circular dependency detection to CI #1346
Conversation
Generated by 🚫 dangerJS |
Codecov Report
@@ Coverage Diff @@
## master #1346 +/- ##
=======================================
Coverage 99.10% 99.10%
=======================================
Files 61 61
Lines 5933 5933
Branches 1347 1347
=======================================
Hits 5880 5880
Misses 52 52
Partials 1 1 Continue to review full report at Codecov.
|
@mtrezza You can create a
|
e68dbe0
to
f3cfa6b
Compare
@dplewis I added this (for
|
Any tips / ideas on how to fixed these? |
The same way I fixed them for Parse Server: think what a sensical dependency tree should look like and refactor accordingly. You want to identify the foundational building blocks of the SDK, which have (or should have) 0 dependencies on other blocks, and work your way up the branches. Always considering that your want to maintain a hierarchical structure. Any dependency that violates that hierarchy needs to be corrected through refactoring. However it seems that there are still type references that are incorrectly detected as circular dep, like |
Adds check to CI that fails on circular dependencies.
Analogous to parse-community/parse-server#7316.
Current circular dependencies that need to be fixed to make the test pass: