routing-filter
Cells
| routing-filter | Cells | |
|---|---|---|
| 1 | 7 | |
| 463 | 3,058 | |
| - | -0.0% | |
| 0.0 | 0.0 | |
| about 2 months ago | 8 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.
routing-filter
-
Why being a developer is frustrating — and why we do it anyway
The problem begins when some of the gems really don't support new Rails version. Like a very nice routing-filter, that we use to simplify handling locale segments in URLs of the website. Unfortunately, this gem relied on very specific internal implementation of Rails routing system, which was largely re-factored in Rails 6.1, completely breaking routing-filter. The last version of routing-filter was released in 2019 and there was not much activity in the repository. So another choice I had is:
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?
rails-i18n - Repository for collecting Locale data for Ruby on Rails I18n as well as other interesting, Rails related I18n stuff
Trailblazer - The advanced business logic framework for Ruby.
Comfortable Mexican Sofa - ComfortableMexicanSofa is a powerful Ruby on Rails 5.2+ CMS (Content Management System) Engine
Amoeba - A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
Mutations - Compose your business logic into commands that sanitize and validate input.
Decent Exposure - A helper for creating declarative interfaces in controllers
Apotomo - MVC Components for Rails.
Responders - A set of Rails responders to dry up your application
dry-transaction - Business transaction DSL
Sequent - CQRS & event sourcing framework for Ruby
dry-types - Flexible type system for Ruby with coercions and constraints