textmood
Light Service
| textmood | Light Service | |
|---|---|---|
| 1 | 5 | |
| 33 | 813 | |
| - | - | |
| 0.0 | 0.6 | |
| over 4 years ago | 6 months 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.
textmood
-
The Ruby Unbundled Series: Services vs. Objects - The Battle for Decomposition and Reuse
The context serves as a bag of attributes that is passed between actions. Each action specifies what attributes it expects as inputs, and what it promises to populate as outputs (if any). The context also includes success indicators and error messages. The code below is used to implement the AnalyzeSentimentAction using the TextMood gem to perform the actual analysis.
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.
What are some alternatives?
eyk-app-templates - A set of basic templates to use as a starting point for EYK applications
Interactor - Interactor provides a common interface for performing complex user interactions.
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
Rectify - Build maintainable Rails apps
Trailblazer - The advanced business logic framework for Ruby.
ActiveInteraction - :briefcase: Manage application specific business logic.
Mutations - Compose your business logic into commands that sanitize and validate input.
u-service - Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.
dry-types - Flexible type system for Ruby with coercions and constraints
Setsy - Settings for classes backed by a database with defaults.
PageletRails - Improve perceived performance of your rails application with minimum effort
Pathway - Define your business logic in simple steps