I left that unchecked, and it emailed them like crazy! The destination category is configured as Watching first post, but before this change those would have been suppressed.
@zogstrip I don’t see test coverage for this case.
In my reading, the describe "silent option" specs only cover the scenarios where the topic being moved is already watched.
The case being described here is for the scenario where the destination category is “watched” or “watching first post”.
@nathank, to my knowledge, we’ve never done that silently.
I think what’s going on here is that the modal for the feature we did add makes it sound like that should also be silenced. I think we’ve shifted expectations with this modal and now we’re not meeting them.
That’s my hunch anyway.
I think this is a legitimate Feature or UX request, and I fully support doing it. But I don’t think it’s technically a bug or a regression.
I had thought this was part of the purpose of including this as an option in bulk actions (to match the behaviour of Disable category edit notifications and Disable tag edit notifications on an ad hoc basis).
The PR itself also makes it sound like that was the intention:
When the “Perform this action silently” checkbox has been checked, the :notify_category_change sidekiq job should not be enqueued.
But I’m not seeing explicit spec coverage for this case.
Admittedly, I’m a bit out of practice readying ruby specs since I haven’t write code day to day for the past few years, but this does feel like a possible gap.
Smells more like a bug to me now. Not sure if regression or not, but does feel like we’re missing coverage for this case.
The @silent option wasn’t propagating properly which caused users watching the destination category to receive notifications even when the “Perform this action silently” checkbox was checked.
Brilliant! And thank you for both taking this seriously and the super quick fix! I’ve just tested it and all seems good.
I just wanted to note that the text in the UI is now different / flipped - so that the ticking the checkbox does the exact opposite of what it used to do. But that side of things seems to be working fine, so hopefully all good.