-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TransientActionFactory
cache simplification
#8048
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/label ready-for-merge
This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!
Causes failures in (at least)
The failures all go away when this change is reverted. The failures all look like more cases of commit 1089a22 (i.e., mocks). The tests could be adapted in the same way, or return ExtensionList.lookup(Cache.class).stream()
.findFirst()
.map(Cache::cache)
.map(classValue -> classValue.get(type))
.map(classValue -> classValue.get(actionType))
.orElse(List.of()); |
More transparent to fix the mock tests I think. Will propose some corrections soon if no one beats me to it. |
As a courtesy I have released Email Extension 2.99. |
* `TransientActionFactory` cache simplification * Fixing mocks in `HistoryPageFilterTest`
Amending #2582 as proposed in #7932 (comment). New implementation is (IMO) simpler and avoids Guava.
Testing done
Just ran
TransientActionFactoryTest
.Proposed changelog entries
Maintainer checklist
Before the changes are marked as
ready-for-merge
:upgrade-guide-needed
label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).lts-candidate
to be considered (see query).