-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Resolve cyclic module dependencies #13025
Comments
It seems that moving some interfaces to the core module or to types would resolve many of these along side the test changes. Would we prefer they move to types or core? |
|
I think any module related interfaces belong in a types or api package rather than core. In my mind, |
Relates to Phase 4 of #11899.
#13012 (comment) identifies all cyclic dependency relationships between
/x/*
modules in the SDK. These relationships must be acyclic for the completion of Phase 4 in the above epic.Tasks
The text was updated successfully, but these errors were encountered: