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
Currently BindingGraphPlugin has only one method visitGraph which gets called for each BindingGraph.
However for component dependencies or any other use cases where we want access to Bindings in another graph currently it is not possible unless annotation processor output is manually post processed. A callback from Dagger when all graphs are processed would be helpful for the SPI plugin to collect all the graphs and perform work in this method where all bindings would be accessible.
This is similar to BindingGraphCapturer used in tests.
Use-case: Binding graph visualizations.
The text was updated successfully, but these errors were encountered:
Currently
BindingGraphPlugin
has only one methodvisitGraph
which gets called for eachBindingGraph
.However for component dependencies or any other use cases where we want access to
Bindings
in another graph currently it is not possible unless annotation processor output is manually post processed. A callback from Dagger when all graphs are processed would be helpful for the SPI plugin to collect all the graphs and perform work in this method where all bindings would be accessible.This is similar to
BindingGraphCapturer
used in tests.Use-case: Binding graph visualizations.
The text was updated successfully, but these errors were encountered: