cli
cli copied to clipboard
ignite
proto cache should break when cosmosgen options are different
If cosmosgen is initialized with different Options, we should consider breaking the cache for proto which means, initialization options should be part of the cache key.
cosmosgen might be initialized differently by a user given configuration in the config.yml file.
the current cache system breaks the cache when user manipulates the generated code or if there was no code generation before for certain parts.
differently, this issue also aims to break the cache when cosmosgen initialized differently, which means there are no manipulations made by the user but cosmosgen now will expected to generate code slightly differently. for example there might be additional dirs added through this Option, through the config file.
