-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit an event after items are manually sorted 馃挴 #11622
Emit an event after items are manually sorted 馃挴 #11622
Conversation
Thanks @infomiho! @benhaynes Thoughts on the event name? |
Yeah, |
Makes sense, I'll update it today to be only |
I'm wondering if we should rather emit |
@nickrum Hmm that's an interesting one. Technically speaking, the sort operation functions differently from a regular update, so there is a case to be made to treat it as a separate event as well 馃 |
I worry about repurposing items.update` if that will save revisions for every sort change. Maybe good to decouple these? 馃 |
One extra argument for decoupling
|
Agreed, I see it the same way. That being said, what Nicola said is also true: Doing the "collection sort was updated" in practice means that the @benhaynes this is unrelated to revisions or revisions tracking, so that doesn't matter 馃憤馃徎 |
2312a0e
to
3cd1e42
Compare
This PR tries to address this discussion #10888
The idea is to add a new action called
sort_update
which can be an extension point for e.g. clearing cache on external CDN.I've tested this locally with a
test
collection and it works as expected.