CustomCacheKeyGenerator does not work as aspected since v4.0.1
Open
relates-to: grails-cache
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
When no key closure is specified, the key generator ignores the targetMethodName. V4.0.0 works fine.
Contributor guide
Research direction
Start by locating CustomCacheKeyGenerator and compare its behavior between Grails v4.0.0 and v4.0.1. Reproduce the case where no key closure is specified, focusing on whether targetMethodName is included in the generated key. Done means the v4.0.1 behavior matches v4.0.0 for this case and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100