Framework, controller and action configuration #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until now, in order to configure the framework, we had direct accessors like
Lotus::Controller. handle_exceptions=
. This design had two main drawbacks:Lotus::Controller
.This new design, adds a class level accessor
.configuration
and a.configure
DSL forLotus::Controller
. Those two methods return an instance ofLotus::Controller::Configuration
.Every time that
Lotus::Controller
gets included in a class, the configuration is copied into the target. The two copies are independent each other.Every time that an action is generated with the
.action
DSL, the controller's configuration gets copied into the target. Again, the two copies are independent each other.This change is also important for Lotus, because it allows to have a micro-services architecture.