4 ms·
(1) Regarding the article: boo f-ing hoo. (2) Why Rails 3.1 actually is blowing it: There is no way to turn off concatenation of js/css files in development!
by eagsalazar 15y ago
(1) Regarding the article: boo f-ing hoo.
(2) Why Rails 3.1 actually is blowing it: There is no way to turn off concatenation of js/css files in development! WTF? Have these guys ever developed a client heavy app before? That is a total non-starter. I love how the entire goal was to make js a first class rails citizen but you can only debug these files in firebug as one giant file! What a f-up!
- xentronium 15y ago> There is no way to turn off concatenation of js/css files in development! Remove these lines: *= require_self *= require_tree . There's another option for really client-side heavy applications -- use better packager; however, it requires some effort to maintain.
- dhh 15y agoThis has already been solved. Just add ?debug_assets=1 to any url and it'll be rendered with individual include lines instead of concatenation. We're building client heavy apps, though, and haven't felt a need for it. But now it's there if you need it. Enjoy!
- eagsalazar 15y agoThat is great news! Rails 3.1 otherwise has many great features. However, I'll be honest, I find it completely unbelievable that you don't have a problem debugging in one huge js file. I guess when using coffee script the connection between what you are debugging and what you are editing is already completely severed so maybe at that point it doesn't matter anymore.
- bxr 15y agoYou have very funny definition of "solve". In my day we would have called that a workaround.
- chriserin 15y agoI find that I like debugging the concatenated version of javascript better. I end up using search a lot more in chrome development tools but I actually get to the place in the code I want to get to faster with one file and search.