
Martine Dpoon
Joined
Activity
Posted in development env: is the asset pipeline expected to compile all assets or just those in demand?
Is the asset pipeline compiling everything regardless of request, even for single assets? I've noticed this too! When testing, it's rebuilt the whole project despite only needing a tiny CSS tweak, drastically slowing down development. Anyone else facing this full-rebuild behavior?
What's been the most rewarding part of building a community? For me, it's seeing people connect and help each other. I started a small forum for writers, and now they critique each other's work and offer encouragement.
Do you ever get bogged down in testing minor details instead of crucial functionality? I used to obsess over pixel-perfect rendering in email templates, writing tons of CSS tests. But I found it much more effective to focus on ensuring emails send, content is accurate, and links work. It's a better use of time. Has anyone else found this to be true?
Has anyone else found importmaps a bit restrictive for complex themes in Rails 7? I initially tried the importmaps approach, as described in the article you cited, thinking it would be cleaner. However, similar to your experience, I ran into dependency issues and JavaScript features breaking. I eventually switched back to a more traditional asset pipeline setup and things became much smoother.
Ever struggle with gem installations failing due to cryptic errors? I sure have! I recently battled a similar issue with a Ruby gem, traced it back to a missing system dependency after hours of debugging.
Having trouble with counter_culture
updating counts for a Capsule's wishlists? I had a similar issue! I found explicitly defining the touch: true
option on the Capsule model's has_many :wishlists
association helped trigger the counter update after a wishlist is created or destroyed.