I just released a small patch version update for CacheMeIfYouCan
I found it was really annoying to root cause bugs caused by the assigns missing deps of a computed property. This is an unfortunately easy scenario to create with this lib due to the dep keys being atoms that can’t be verified against the assigns at compile time. I ran into this a couple times after refactoring some code and forgetting to rename the dep keys.
This change adds a Logger.warning message when calling assign_cached would result in skipping the recomputation of the property due to a dep key missing in the current assigns. This should make it easier to identify the reactive cache as the cause of state bugs earlier.
I may add an assign_cached! throwing version in the future which would crash in this scenario instead of just logging a warning, but I need to think a bit more about that still.
