me
/
glitchier-soc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7317b7b231'
${ noResults }
glitchier-soc/app/views/settings/keyword_mutes/index.html.haml

20 lines
688 B
Raw Normal View History Unescape

Set up /settings/keyword_mutes. #164. This should eventually be accessible via the API and the web frontend, but I find it easier to set up an editing interface using Rails templates and the like. We can always take it out if it turns out we don't need it.
7 years ago
- content_for :page_title do
= t('settings.keyword_mutes')
Spike out index and new views for keyword mutes controller.
7 years ago
.table-wrapper
%table.table
%thead
%tr
Fill in create, edit, update, and destroy for keyword mutes interface. Also add a destroy-all action, which can be useful if you're flushing an old list entirely to start a new one.
7 years ago
%th= t('keyword_mutes.keyword')
%th= t('keyword_mutes.match_whole_word')
Add apply-to-mentions option to keyword mute UI. #454.
7 years ago
%th= t('keyword_mutes.apply_to_mentions')
Spike out index and new views for keyword mutes controller.
7 years ago
%th
%th
%tbody
Override Action View name inference in settings/keyword_mutes. 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.
7 years ago
= render partial: 'keyword_mute', collection: @keyword_mutes, as: :keyword_mute
Spike out index and new views for keyword mutes controller.
7 years ago
= paginate @keyword_mutes
Fill in create, edit, update, and destroy for keyword mutes interface. Also add a destroy-all action, which can be useful if you're flushing an old list entirely to start a new one.
7 years ago
.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') }