Add support for Rails::Engine

[zlw]

Hi 👋

Note: This PR builds on top on previous PR where I added support for latest dry-system, but I can't do stacked PRs here 😢 Going through the commits (1st commit - previous PR, 2nd - this PR) might give cleaner diff 🙌

---

Added experimental support for Rails::Engine

Adding dry-rails to monolith Rails app works like a charm 🥇

However, it's not so great when used with Engines

• There's no way for an Engine to define its own Container
• There's no way to not have Container for main app (sounds odd but that's actually our use case, we want to have DRY-rb setup only in one Engine)

I think each Engine should define its own Container, otherwise we're loosing whole namespace isolation that Engines provide

MainApp::Container.resolve('users.create')        #> Dry::Container::Error: Nothing registered with the key "users.create"
SuperComponent::Container.resolve('users.create') #> #<SomeComponent::Users::Create:0x00007fa6d963e368>

[zlw]

this is a bit puzzling tbh, when I do: Dry::Rails::Engine.container(...) { do something with container } it's not available until reload! call Finalizer and evaluates the config again 🤔 ("worked like that before")

would the same happen if container is used eg. in before_filter - changes done to container would "leak" into next request? this doesn't sound right... 😅

[solnic]

@zlw setting up container should only be available during app's booting phase. Once it's done, we should literally freeze its config (which I believe already happens?)

[solnic]

Please rebase this against the latest master as your other PR got just merged 🙂

[zlw]

@solnic done 👌 it should be ready to go now 🙌

[solnic]

@zlw thanks, this is something we should definitely support. Personally I don't use engines at the moment, which means I won't be able to help with this other than to provide some basic feedback in this PR + release it. If we get this merged and released and it turns out it breaks things, you'd have to own it and fix things though. Otherwise I would have to revert the entire feature because I wouldn't have time to deal with any potential fixes.

[zlw]

@solnic no worries, if something arises from this - I'll do my best to fix it 👌 😄