actor
ActiveInteraction
| actor | ActiveInteraction | |
|---|---|---|
| 3 | 6 | |
| 637 | 2,039 | |
| - | - | |
| 7.7 | 2.5 | |
| 3 days ago | 27 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
actor
-
Is using a single hash as my only param in service objects a good idea?
Avoid using hash as the only input for your class initializer signature. Moreover a service object is meant to serve as a stateless function so you should avoid initializing it. You should use Service#call as only public interface (see this beautiful gem for more details: https://github.com/sunny/actor)
-
Utilizando o padrão interactor no Ruby on Rails
View on GitHub
-
Is there a Gem to help skinny up controllers?
I found that https://github.com/sunny/actor offers the simplest approach. It’s really nice. Has nice DSL methods and enforces some rules.
ActiveInteraction
-
The Decree Design Pattern
One of the first things I plug into any new or inherited rails project over the last few years is ActiveInteraction.
-
Applying the Use Case Pattern with Rails
The Interactor and ActiveInteraction gems are both great libraries for implementing this pattern.
-
Is there a Gem to help skinny up controllers?
I guess that ActiveInteraction is what you're looking for: https://github.com/AaronLasseigne/active_interaction
-
How does Application Interaction runs 'execute' function?
Skimming the README, it looks like you can pass a lambda as a default:
-
Rails application boilerplate for fast MVP development
active_interaction to make controllers thin
-
How can I ask the controller to ask another controller to call one of its actions? Without violating the SRP?
I prefer building "interactions" these days (specific, single-purpose "services" that are easily callable and composable), using https://github.com/AaronLasseigne/active_interaction
What are some alternatives?
Interactor - Interactor provides a common interface for performing complex user interactions.
assets - Assets management for Ruby web applications
Trailblazer - The advanced business logic framework for Ruby.
Hanami::Model - Ruby persistence framework with entities and repositories
Mutations - Compose your business logic into commands that sanitize and validate input.
router - Ruby/Rack HTTP router
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
actor-rails - Actor Rails provides Rails support to the Actor service objects
Light Service - Series of Actions with an emphasis on simplicity.
flow - Write modular and reusable business logic that's understandable and maintainable.
PageletRails - Improve perceived performance of your rails application with minimum effort