Translate Ecto validation messages

hubertlepicki · May 27, 2017, 6:03am

If you used mix phoenix.new generator, it already created the required functions and infrastructure for you. If you open your generated error_helpers.ex you will find translate_error/1 function there that does what you want. You can use it directly in your views/templates (or import it in other places if you need to move to different layer). It takes the tuple with string and options, which is exactly what Ecto validations return.

Here is the template for reference:

github.com

phoenixframework/phoenix/blob/e39f718429af9b693dd2141981fa7360d8d92ea8/installer/templates/new/web/views/error_helpers.ex

defmodule <%= app_module %>.ErrorHelpers do
  @moduledoc """
  Conveniences for translating and building error messages.
  """
<%= if html do %>
  use Phoenix.HTML

  @doc """
  Generates tag for inlined form input errors.
  """
  def error_tag(form, field) do
    Enum.map(Keyword.get_values(form.errors, field), fn (error) ->
      content_tag :span, translate_error(error), class: "help-block"
    end)
  end
<% end %>
  @doc """
  Translates an error message using gettext.
  """
  def translate_error({msg, opts}) do

This file has been truncated. show original

Please note that if you do use the error_tag/2 function from the same module, it already translates the errors for you.

You should already have the translations template file in priv/gettext/errors.pot, and you can put in the translations you want to say priv/gettext/fr/LC_MESSAGES/errors.po