Hi Grant, glad you're enjoying the SDK!

The 2nd link you gave should be fairly simple to refactor, just replace Temporal.configuration.namespace with @config.namespace.

For the third link you don’t need to refactor anything, just pass in a configuration object instead of using the default option when creating your worker.

The first link requires a pretty big refactor if I remember right, I’ll let @antstorm chime in on how to approach that one.

@gshively11 agree with what DeRauk said above. The first link is definitely a bigger refactor project, but should also be doable. I think the best approach there is to make payload converters (Temporal::Concerns::Payloads) part of the configuration instead of a mixin and then ensure that configuration is propagated where needed.

We can also avoid breaking changes by having one or two places where we fallback onto default configuration if nothing else is provided, but it should be at the top level and would result in minimal output noise.

I'm happy to assist you with the PR or I can take a look at it next week in case you feel like it might be a bit too much.

Thanks for chiming in @DeRauk and @antstorm. I can give the PR a try, although it might be weeks before I get around to it due to other responsibilities. If this is something you (or anyone) wants to fix sooner, feel free to grab it, just drop a comment letting me know.

@gshively11 I might have some time to pick it up this week. Will ping you on the PR

For other travelers wondering how to silence this, I ended up not caring about this message (it has been 'deprecated' for over 2 years now, afterall).

I added this to my config/initializer/temporal.rb file in my rails app:

def Temporal.warn(msg)
  Rails.logger.warn(msg)
end

Voilá - no more warnings.

(I know this is bad, I just couldnt take it anymore)