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.master
parent
641f90e73a
commit
9226257a1b
@ -1,6 +1,6 @@ |
||||
- content_for :page_title do |
||||
= t('keyword_mutes.edit_keyword') |
||||
|
||||
= simple_form_for @keyword_mute, url: settings_keyword_mute_path(@keyword_mute) do |f| |
||||
= simple_form_for @keyword_mute, url: settings_keyword_mute_path(@keyword_mute), as: :keyword_mute do |f| |
||||
= render 'shared/error_messages', object: @keyword_mute |
||||
= render 'fields', f: f |
||||
|
@ -1,6 +1,6 @@ |
||||
- content_for :page_title do |
||||
= t('keyword_mutes.add_keyword') |
||||
|
||||
= simple_form_for @keyword_mute, url: settings_keyword_mutes_path do |f| |
||||
= 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 |
||||
|
Loading…
Reference in new issue