path for form helper about i18n-active_record

[timfjord]

In general, that fact that the i18n_backend_active_record_translation_path is not defined but the translations_path is has nothing to do with the initializer.
translations_path works only because you have an entry in routes.rb that defines a route named translations, so if you add something like

get '/something' => 'my_controller#my_action', as: :i18n_backend_active_record_translation

most likely it will work without url: translations_path

You can also try

class Translation < I18n::Backend::ActiveRecord::Translation
end

Adding the note about the path helper might be confusing because this gem doesn't really add routes and controllers and acts purely as a backend for I18n gem.

[D4v1dW3bb]

I changed `Translation = I18n::Backend::ActiveRecord::Translation` In the initializer to: ``` class Translation < I18n::Backend::ActiveRecord::Translation end ``` An now it works as expected. I think it’s wise to change this in the default `I18n_active_record.erb` Regards, Didier From: Tim Masliuchenko <[email protected]> Sent: Tuesday, May 19, 2020 2:18 AM To: svenfuchs/i18n-active_record <[email protected]> Cc: D4v1dW3bb <[email protected]>; Author <[email protected]> Subject: Re: [svenfuchs/i18n-active_record] path for form helper (#105) In general, that fact that the i18n_backend_active_record_translation_path is not defined but the translations_path is has nothing to do with the initializer. translations_path works only because you have an entry in routes.rb that defines a route named translations, so if you add something like get '/something' => 'my_controller#my_action', as: :i18n_backend_active_record_translation most likely it will work without url: translations_path You can also try class Translation < I18n::Backend::ActiveRecord::Translation end Adding the note about the path helper might be confusing because this gem doesn't really add routes and controllers and acts purely as a backend for I18n gem. — You are receiving this because you authored the thread. Reply to this email directly, <#105 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AB2SQHR62CE47FTBNGYZNXDRSI6C7ANCNFSM4NENESQQ> unsubscribe. <https://github.com/notifications/beacon/AB2SQHWM3PXXFMSGD4CJZSLRSI6C7A5CNFSM4NENESQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEWLSQFA.gif>

[timfjord]

It is not recomennded to keep class Translation < I18n::Backend::ActiveRecord::Translation in the initializer, it should be in app/models/translation.rb
Basically this way we define our own AR model but inherit from the model from the gem.
I shared that just to illustrate that the issue wasn't really related to the initializer.

It is expected that I18n::Backend::ActiveRecord::Translation returns i18n_backend_active_record_translation_path.
Usage of the model in helpers like form_for or link_to is not supported because this gem doesn't provide any controllers, routes to handle that.

[D4v1dW3bb]

It is expected that I18n::Backend::ActiveRecord::Translation returns i18n_backend_active_record_translation_path.
Usage of the model in helpers like form_for or link_to is not supported because this gem doesn't provide any controllers, routes to handle that.

The gem does not provide it but it's expected the users of the gem are going to use it. Their not going to fill the translation table by hand. so they will need to make controllers, views and routes. Therefor the translation table should act like every other model whether it's installed by a gem or the programmer implements it himself.

[timfjord]

You can use i18n_backend_active_record_translation name in your routes because this is what the model generates.

But I am going to revisit Translation = I18n::Backend::ActiveRecord::Translation part in the initializer and probably include class Translation < I18n::Backend::ActiveRecord::Translation model instead.

[floydj]

You can use i18n_backend_active_record_translation name in your routes because this is what the model generates.

So how exactly is this done?

[timfjord]

You can use i18n_backend_active_record_translation name in your routes because this is what the model generates.

So how exactly is this done?

The easiest way is to have something like this in the routes.rb:

post '/some_path', to: 'my_controller#my_action', as: 'i18n_backend_active_record_translation'

But the custom model should be more convinient