Rearchitect lazy loading registry cache #818
Labels
help wanted
Need some extra hands to get this done.
status/ready
Issue ready to be worked on.
type/chore
Issue that requests non-user facing changes.
Side tantrum: I have issues with the architecture decision. I'm not seeing the value of lazy loading the cache in this case. I think a better pattern may be to differentiate between a RegistryCache "config" and an "initialized" RegistryCache. Any time a
RegistryCache
is provided it should already be initialized. ARegistryCacheConfig
can be used in cases where we just want to provide configuration without necessary interaction.Originally posted by @jromero in #782 (comment)
The text was updated successfully, but these errors were encountered: