It is only a problem when a chain goes from not using depinject to using depinject right?

We could update runtime to purposely skip tx when calling

Is that really a problem? If so then we would need to add a field to denotate that a module doesn't have a store key in app_config (

We could update runtime to purposely skip tx when calling

cosmos-sdk/runtime/module.go

Line 205 in fc84ff6

func registerStoreKey(wrapper *AppBuilder, key storetypes.StoreKey) {

, but this is an issue for all modules that aren't actually modules or that just don't need to save state.
Is that really a problem? If so then we would need to add a field to denotate that a module doesn't have a store key in app_config (

cosmos-sdk/api/cosmos/app/runtime/v1alpha1/module.pulsar.go

Line 2064 in fc84ff6

type Module struct {

)

hmm, is there anyway to make this part of depinject? seems we are uncovering edge cases that may prevent users from using depinject. IBC also has a case

hmm, is there anyway to make this part of depinject?

This has nothing to do with depinject, but a runtime v1 assumption, which requires a runtime change.
Personally, I prefer the option 2, as I can imagine multiple modules having no store.

option 2 seems the best, we just need to document it 👍