Trailblazer
Cells
Our great sponsors
| Trailblazer | Cells | |
|---|---|---|
| 2 | 7 | |
| 3,386 | 3,058 | |
| 0.3% | -0.0% | |
| 5.1 | 0.0 | |
| 4 months ago | 8 months ago | |
| Ruby | Ruby | |
| GNU Lesser General Public License v3.0 only | 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.
Trailblazer
-
Applicative programming in Ruby: railway reimagined
Did you check Trailblazer framework ?
-
Business logic in Rails with operators
I can’t say I was not influenced by other solutions. For example, I used Trailblazer before. But none of what I read about or used was the one I would like.
Cells
-
The Admin Framework for Minimalist
It can be used with Ruby on Rails or other frameworks because I implemented with trailblazer/cells.
-
Is ViewComponent the Future of Rails?
I agree, though cells does still have a larger following.
Better official documentation for cells: https://trailblazer.to/2.1/docs/cells.html
-
From partials to ViewComponents: writing reusable front-end code in Rails
So what about the world outside Rails defaults? There are quite a few independent projects trying to help build components in the Rails view layer, among the more famous being Draper (utilizing the decorators pattern) or Cells (full-featured components in views). In the end, we decided to take a deeper look into a relatively new one – the ViewComponent framework.
-
Cells - Introduction
GitHub has recently posted an article about view_component: https://github.blog/2020-12-15-encapsulating-ruby-on-rails-views/ Before it gets too popular I think I should share my experience with cells So that developers can have another chance to re-think and pick what to use for "encapsulated view components".
-
Why being a developer is frustrating — and why we do it anyway
This, combined with the fact that we are using cells gem for some view components, resulted in another couple of hours of hunting for the problem (it takes some time to debug what exactly and how exactly changed in Rails internals) and then fixing this problem. At this moment, I already spent over 8 hours debugging Rails internals, different gem internals, fixing application, fixing tests, screaming internally.
What are some alternatives?
Interactor - Interactor provides a common interface for performing complex user interactions.
Amoeba - A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model
dry-transaction - Business transaction DSL
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
ActiveInteraction - :briefcase: Manage application specific business logic.
Mutations - Compose your business logic into commands that sanitize and validate input.
Rectify - Build maintainable Rails apps
Decent Exposure - A helper for creating declarative interfaces in controllers
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Apotomo - MVC Components for Rails.
Light Service - Series of Actions with an emphasis on simplicity.
Responders - A set of Rails responders to dry up your application