dry-system
dry-system copied to clipboard
dry-rb
Application framework with state management and built-in dependency injection support
I think I managed to make it work without warnings. We should merge this PR once we're ready to cut a release.
Right now, the only way is to do this: ```ruby config.component_dirs.add "some_dir" do dir.auto_register = proc do |component| relative_path = component.file_path.relative_path_from(root).to_s !relative_path.start_with?("config#{File::PATH_SEPARATOR}") end end ``` Which feels a bit too...
We can use this for at least these three places (and we can add type checking to require that the given value is either `:root` or a `String`, and nothing...
Let me know whether the error should have another name, I thought the name `ContainerAlreadyFinalizedError` is adequate as it can be reused in the future for any operation on a...
This would also mean we don't need to worry about handling this error from the Hanami side of dry-system usage.
dry-system provides a nice container for creating new instances of classes, but it doesn't enforce its use. Developers are free to create an object by calling its constant constructor (e.g....
The `:injector_mixin` plugin makes it an easy one-liner to define a constant for the given container's auto-injector mixin. This way you never have to worry about doing `Deps = MyContainer.injector`...
This PR adds a glossary ([readable version here](https://github.com/dry-rb/dry-system/blob/add-glossary/docsite/source/glossary.html.md)) covering all key dry-system concepts and features. This should eventually be merged into the documentation, ideally as part of a revamp that...
