You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the great plugin! While i haven't been able to explore it in my project because of the limitation of it not having support of ksp processor. But, the visualisation from the docs looks great with ability of interactive flow using svg.
I wonder if it's possible to extend the capability of this project by using dagger-spi to make it easier by
Resolving circular dependency - the stack-trace gives enough detail in figuring out where the circular dependency lies, but when deep down in the DAG for large project, it becomes difficult for beginners reading the stack-trace and figuring out, where the cycle is formed and the mitigation strategy. Give an easy to read text to show where/how the circular dependency is formed and which gradle projects or dagger @provides might be the cause of it.
Resolving Dependendency not found - certain times, dagger throws error if it doesn't find the dependency in the DAG because of wrong scoping or forgot to add the object in DAG or bind it. Advice, what module needs to be added if they are present in the gradle project or what wiring should be provided manually.
Haven't thought it through and i am unsure if this project is only focused as a visualization tool, but having something like that would be nice to have.
The text was updated successfully, but these errors were encountered:
Thanks for the great plugin! While i haven't been able to explore it in my project because of the limitation of it not having support of ksp processor. But, the visualisation from the docs looks great with ability of interactive flow using svg.
I wonder if it's possible to extend the capability of this project by using
dagger-spi
to make it easier byResolving circular dependency - the stack-trace gives enough detail in figuring out where the circular dependency lies, but when deep down in the DAG for large project, it becomes difficult for beginners reading the stack-trace and figuring out, where the cycle is formed and the mitigation strategy. Give an easy to read text to show where/how the circular dependency is formed and which gradle projects or dagger @provides might be the cause of it.
Resolving Dependendency not found - certain times, dagger throws error if it doesn't find the dependency in the DAG because of wrong scoping or forgot to add the object in DAG or bind it. Advice, what module needs to be added if they are present in the gradle project or what wiring should be provided manually.
Haven't thought it through and i am unsure if this project is only focused as a visualization tool, but having something like that would be nice to have.
The text was updated successfully, but these errors were encountered: