Light Service
actor
Our great sponsors
| Light Service | actor | |
|---|---|---|
| 5 | 3 | |
| 813 | 633 | |
| - | - | |
| 0.6 | 7.7 | |
| 5 months ago | 6 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.
Light Service
-
The Decree Design Pattern (Ruby on Rails)
check out the `light-service` gem - it lets you create services that use this pattern and compose them into complex flows: https://github.com/adomokos/light-service
-
How to avoid if/else with different ramifications
Similar to the above recommendations of Railway Orientated Programming and the Interactor gem, I use the Light Service gem. While it can sometimes be a bit verbose it excels in code reuse, testability, and composition.
-
Utilizando o padrão interactor no Ruby on Rails
View on GitHub
-
Ten Ruby gems for Rails you should definitely know about
LightService
-
The Ruby Unbundled Series: Services vs. Objects - The Battle for Decomposition and Reuse
You can implement the service pattern as a PORO, but it helps to use one of the gems available to aid in code structure, orchestration, and error handling. The LightService gem provides a nice implementation without adding hardly any overhead. It’s design is very simple, as shown in the diagram below. An organizer is used to define the sequential workflow, which is made up of one or more actions. An error in any of the actions will short-circuit the entire workflow.
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.
What are some alternatives?
Interactor - Interactor provides a common interface for performing complex user interactions.
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
assets - Assets management for Ruby web applications
Rectify - Build maintainable Rails apps
Hanami::Model - Ruby persistence framework with entities and repositories
Trailblazer - The advanced business logic framework for Ruby.
router - Ruby/Rack HTTP router
ActiveInteraction - :briefcase: Manage application specific business logic.
actor-rails - Actor Rails provides Rails support to the Actor service objects
Mutations - Compose your business logic into commands that sanitize and validate input.
flow - Write modular and reusable business logic that's understandable and maintainable.