Assume Glitch::KeywordMute#destroy! works and error out if it doesn't.

There's nothing useful we can display if the destroy action messes up,
so might as well assert it does and complain loudly if it doesn't.
remotes/1727458204337373841/tmp_refs/heads/signup-info-prompt
David Yip 2017-10-24 18:56:57 -05:00
parent d5c8ebe205
commit d9485e6497
1 changed files with 3 additions and 6 deletions

View File

@ -33,12 +33,9 @@ class Settings::KeywordMutesController < ApplicationController
end
def destroy
if @keyword_mute.destroy
redirect_to settings_keyword_mutes_path, notice: I18n.t('generic.changes_saved_msg')
else
# FIXME
redirect_to settings_keyword_mutes_path, notice: "huh that didn't work right"
end
@keyword_mute.destroy!
redirect_to settings_keyword_mutes_path, notice: I18n.t('generic.changes_saved_msg')
end
def destroy_all