7caca589c1
Glitch::KeywordMute's name is inferred as glitch_keyword_mutes, and in templates this turns into e.g. settings/glitch/keyword_mutes. Going along with this convention means a lot of file movement, though, and for a UI that's as temporary and awkward as this one I think it's less effort to slap a bunch of as: options everywhere. We'll do the Right Thing when we build out the API and frontend UI.
18 lines
638 B
Text
18 lines
638 B
Text
- content_for :page_title do
|
|
= t('settings.keyword_mutes')
|
|
|
|
.table-wrapper
|
|
%table.table
|
|
%thead
|
|
%tr
|
|
%th= t('keyword_mutes.keyword')
|
|
%th= t('keyword_mutes.match_whole_word')
|
|
%th
|
|
%th
|
|
%tbody
|
|
= render partial: 'keyword_mute', collection: @keyword_mutes, as: :keyword_mute
|
|
|
|
= paginate @keyword_mutes
|
|
.simple_form
|
|
= link_to t('keyword_mutes.add_keyword'), new_settings_keyword_mute_path, class: 'button'
|
|
= link_to t('keyword_mutes.remove_all'), destroy_all_settings_keyword_mutes_path, class: 'button negative', method: :delete, data: { confirm: t('admin.accounts.are_you_sure') }
|