Support configuring custom keys via method invocation #84
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support to generate keys via a method name passed as a symbol:
Currently, the only way to customize keys is via a lambda, lilke
key: ->(p) { "person:#{p.id}:names_customized" }
. The problem with that approach is that, when you want to invoke a method to determine the key, you need to make that method public. This is also a more concise way of covering a pretty common use case: using an instance method to determine keys.