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
@AppScope
something.Cool <- something.CoolImpl
com.ReplaceMe <- com.ReplaceMeImpl (**REPLACED**) <- com.IReplacedYou // Calls out what it is replacing
@ActivityScope
something.Else <- something.ElseImpl
standalone.Impl <- standalone.Impl // Provided as a concrete type
This sort of baseline would be incredibly useful in many cases and for debugging.
Writing out replaces is also something that would be nice to call out in bindings. I've seen bugs and issues come up when it wasn't known that a replaces was happening.
This file could be generated per module.
This file would get noisy in Git. Maybe just having the replaces only in the baseline by default would be good?
The text was updated successfully, but these errors were encountered:
I wanted to call it baseline because like Android lint or dependency-guard, I'd want to see in source control that my baseline changed.
This is because it's so easy to introduce a replaces and have no idea it's happening.
I was on a project previously where an important upgrade checking feature was being replaced by a fake implementation and it was undiscovered for a year.
For my use case, a report could be useful, but wouldn't help me automatically detect these sorts of changes.
Could you generate a file that contains the following (see snippet) using
anvil/compiler/src/main/java/com/squareup/anvil/compiler/codegen/BindingModuleGenerator.kt
Lines 58 to 60 in aa24f31
This sort of baseline would be incredibly useful in many cases and for debugging.
Writing out
replaces
is also something that would be nice to call out in bindings. I've seen bugs and issues come up when it wasn't known that a replaces was happening.This file could be generated per module.
This file would get noisy in Git. Maybe just having the
replaces
only in the baseline by default would be good?The text was updated successfully, but these errors were encountered: