re: A Nifty Use Case for Rails Virtual Attributes VIEW POST



Out of curiosity, why are you using models to represent frontend components instead of View Components?


The project is older than view components, so we never really got around to adding them to the project. Around the time we finished the first big deployment, I read an article about view components and was like "Hey! That's exactly what we're doing with our component system!" But we already have all our stuff in place and it's working well.

Code of Conduct Report abuse