i18n support for scaffolds? about rails HOT 2 CLOSED

@yshmarov, I've suggested this before, but ended up not writing the PR, because someone on Rails core (I believe DHH), mentioned that the scaffold are intentionally "ugly" or bare. They are not intended to be used as is. You are expected to modify them heavily.

In practice, I found that a lot of those modifications where very repetitive, so I wrote a set of generators to handle it for me.

I think that there is a case to be made for upstreaming something like this. Although, it would likely be an an uphill battle.

I rely a lot less on scaffolds than I use to, but I think there is good reasons to use the I18n layer even without translating the app. It let you separate copy from the code.

Take this controller action for example:

def update
    if @book.update(book_params)
      redirect_to @book, notice: success_message(@book)
    else
      render :edit, status: :unprocessable_entity
    end
end

and the helper implementation:

  def success_message model = nil
    args = {}
    args[:name] = model.model_name.human if model
    t(".success", default: :"application.#{action_name}.success", **args)
  end

This lets me

• have a generic success message that adapts automatically to the model name.
• I can change the model name showed to the user independently from how it is called in the code.
• I can write custom success message per model if needed.
• The controller doesn't have to worry about copy. It is only focused on returning a success message. It doesn't have to care what the success message is.

I'll try to post my generators soon™ and I'll open the discussion again.

from rails.

Thank you for the suggestion but we reserve the issue tracker for bugs only. For feature requests/discussion the best place would be the forums

from rails.