actor
Composable Ruby service objects (by sunny)
view
Views, templates and presenters for Ruby web applications (by hanami)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of actor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-20.
-
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.
view
Posts with mentions or reviews of view.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-20.
-
Utilizando o padrão interactor no Ruby on Rails
Hanami::View - Presentation with a separation between views and templates
What are some alternatives?
When comparing actor and view you can also consider the following projects:
Interactor - Interactor provides a common interface for performing complex user interactions.
standard - Ruby's bikeshed-proof linter and formatter 🚲
assets - Assets management for Ruby web applications
u-service - Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.
Hanami::Model - Ruby persistence framework with entities and repositories
router - Ruby/Rack HTTP router
flow - Write modular and reusable business logic that's understandable and maintainable.
actor-rails - Actor Rails provides Rails support to the Actor service objects
Mutations - Compose your business logic into commands that sanitize and validate input.
validations - Validation mixin for Ruby objects