puyopuyotetr.is/app/views/settings/keyword_mutes/new.html.haml

- content_for :page_title do
  = t('keyword_mutes.add_keyword')

= simple_form_for @keyword_mute, url: settings_keyword_mutes_path, as: :keyword_mute do |f|
  = render 'shared/error_messages', object: @keyword_mute
  = render 'fields', f: f
Spike out index and new views for keyword mutes controller. 2017-10-15 18:51:42 +09:00			`- content_for :page_title do`
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. 2017-10-21 05:12:45 +09:00			`= t('keyword_mutes.add_keyword')`
Spike out index and new views for keyword mutes controller. 2017-10-15 18:51:42 +09:00
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. 2017-10-25 08:40:28 +09:00			`= simple_form_for @keyword_mute, url: settings_keyword_mutes_path, as: :keyword_mute do \|f\|`
Spike out index and new views for keyword mutes controller. 2017-10-15 18:51:42 +09:00			`= render 'shared/error_messages', object: @keyword_mute`
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. 2017-10-21 05:12:45 +09:00			`= render 'fields', f: f`