ruban-gt / qudo Goto Github PK

Create property for container with default components config.

Need to rename call method of Qudo::Component instance, because it's not meaning of calling of object, it's returns object. Maybe prepare, resolve will be better name.

Think about components with only one public interface: call or exec (or something similar) that calculate some result
It doesn't require builder and may be I need to disable requiring of it.

May be would be useful to can register a only one component with one unique key with special class option.

Allow to use common classes or procs for container.

• Also pass extra args to initializer of class input.

Move external dependencies to constructor and default methods.

• Aliases for Container and Application for working with a store
• A container method for quick getting of a target

From dry-struct to dry-initializer

Before creation main structures (#3), I need to do some experiments, proposals on how the project should look like.
After this I can make a list new required features for comfortable working with Qudo.

Write README for the project.

Implementation of Qudo::Container class as component register and upgrade components by IoC concept with dependencies.

Implement Qudo::System as application container.

Implement Qudo::Application as top-level of umbrella-application.

I can choose one of them:

• https://github.com/hamstergem/hamster
• https://github.com/ruby-concurrency/concurrent-ruby

Also allow to fill needed path(s) in this option.

Think about a mechanism for auto-registration of components

Allow to set an opportunity to initialize default empty container for inherited class of Application

Think about creation of cli that can generate a skeleton, applications, containers, components and configuration.