-
Notifications
You must be signed in to change notification settings - Fork 14
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
Investigate using madge to detect circular dependencies in our codebase #1557
Comments
It brought up the following circular dependencies. Notably, there are some in scenerystack code which did not get caught by other tooling:
|
@zepumph thoughts on how to handle the non-sim circular dependencies? |
Hey. I love this script! Thanks so much for making it. I moved it over to scripts/ because I'm trying to keep grunt/ as the list of public tasks we would want to communicate to all devs (and mostly even to public, non phet, devs). It's a bit arbitrary, but thanks for you patience. I think we should work on joist first (the only common code). And then discuss next steps at dev meeting. |
Most of the ones I solved where just adding "type" to the import. Yay!
Common code left:
Let's discuss at dev meeting for a progress report. @jonathanolson, can you please post here some of the benefits of handling all of these, and if the benefits differ between common code and sim-specific circles. |
Also noting that if we solve everything, then we can turn on phetsims/perennial#432 perhaps quite a bit easier. |
Probably we want to think about this issue in the same conversation as phetsims/perennial#432. When I applied the |
After committing the auto fix over in phetsims/perennial#432 to axon and CCKC, we are down to 30 problems:
|
This should be similar to how this is done for scenerystack.
The text was updated successfully, but these errors were encountered: