-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Circular dependency between base-widget.ts and gridstack.component.ts #2955
Comments
I see BaseWidget doing |
We have seen enough circular dependencies in the last few years to know that the order of imports can also matter for either seeing an error or not. So perhaps import changes of any of the dependencies might be the reason the problem never appeared before. |
* fix gridstack#2955 * moves ng types into it's own plain file, fix order of include/export to reflect heirachy Note: gridComp depends on gridItem but not other way around
hopefully fixed in next release... |
There is a circular dependency between gridstack.component.ts and base-widget.ts, which in some scenarios will lead to errors. One of those scenario's can be found in the example below where we cannot extend from BaseWidget.
Worth mentioning is that we have other unit tests and other code in the same codebase that extend BaseWidget without any problems.
The issue was discovered in version 11.3.0, but has likely existed long before.
Example.
test-base-widget.spec.ts (jest unit test)
Running this unit test will throw the following error:
We have seen similar weird issues in the past with other code that were eventually tracked down to be caused by Circular Dependencies and often those circular dependencies had existed for a longer period of time, it just never manifested in errors before.
So it is just a matter of time before actual issues occur in other parts of a client's codebase.
The text was updated successfully, but these errors were encountered: