Recommended pattern for 3.0+ use with dry-initializer and default options

[wooly]

Hey gang,

Up until the update to 3.0, we've been using a pattern like this to define our view components with default values:

# frozen_string_literal: true

module ModalFooter
  class Component < ApplicationComponent
    extend Dry::Initializer

    option :close_title, default: proc { t('action.cancel') }
  end
end

With the upgrade to 3.0, this is now raising a ViewComponent::TranslateCalledBeforeRenderError because of the way I assume the dry-initializer gem works internally.

Does anyone have any bright ideas on a neat way to solve this such that we can maintain the declarative API that we have but not raise the error? I'd rather not update all the call-sites to mitigate the use of the default. I guess the only way would be to make it optional and then in a before_render hook fall back to the cancel translation if it isn't provided?

[Spone]

I think this issue has been introduced in #1666. If this worked previously, I'm not sure whether we need to prevent calling translate in the context of a dry-initializer default value. Any thoughts @joelhawksley @elia?

I guess the only way would be to make it optional and then in a before_render hook fall back to the cancel translation if it isn't provided?

That seems like a reasonable workaround, but I understand it's not ideal to force you to change the option declarations in all your components.

[joelhawksley]

@Spone the reason we made that change in #1666 is that translate did not have access to all translations until a view context is present at render time, so some translations would work in the initializer and others would not.

[Spone]

Understood, so I guess there's no way to still use translate in dry-initializer declarations, since the proc is called when the component is initialized, not rendered.