Amoeba
Cells
Amoeba | Cells | |
---|---|---|
3 | 7 | |
793 | 3,058 | |
0.9% | -0.1% | |
4.3 | 0.0 | |
27 days ago | 8 months ago | |
Ruby | Ruby | |
BSD 2-clause "Simplified" 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.
Amoeba
- Ways to enable the users of my app to duplicate/copy their records?
-
Accessing [grand+]child through multiple queries VS having direct reference to the [grand+]parent on every model.
What made me think about this is that I'm using (maybe in the wrong way) some gems like Blueprinter and Amoeba.
- duplication for join table
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?
Clowne - A flexible gem for cloning models
Trailblazer - The advanced business logic framework for Ruby.
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
Lionshare - A Ruby interface to the Lionshare API (cryptocurrency prices)
Mutations - Compose your business logic into commands that sanitize and validate input.
Apotomo - MVC Components for Rails.
Decent Exposure - A helper for creating declarative interfaces in controllers
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
PageletRails - Improve perceived performance of your rails application with minimum effort
Responders - A set of Rails responders to dry up your application