Interactive "rails new"
dhh discuss ruby on rails · 2020-05-10
That sounds like a great idea! If we’re letting you run stuff straight from a URL, we should probably preview what you’re about to run. But
That sounds like a great idea! If we’re letting you run stuff straight from a URL, we should probably preview what you’re about to run. But
I did a survey at the time of Webpacker, and I do think we looked at Parcel. But I don’t recall why we didn’t go that route. The basic premi
We use script/migrate/* at Basecamp. It’s just a basic script that starts with: require_relative "../../config/environment" We also have s
Also, I don’t think there’s a zero sum here. A good idea doesn’t have to justify itself with what it would replace, like “be more beneficial
Devise is good for the omnibus, but I’d like to make more of the core ingredients directly accessible. Like we did with has_secure_password.
We have a complete API to do this: Rails.backtrace_cleaner.add_silencer { |line| /my_noisy_library/.match?(line) } But we haven’t updated
I’m a big fan of backtrace cleaning! I don’t think we’ve upgraded our standard backtrace cleaning to account for neither spring nor bootstra
Betsy, you mean that DiskService should have been called LocalService or even TestService to emphasize its intentions? I could see that. But
I like the idea of have the guide walk you through “here’s how to serve from your own controller”. We tell you that this is what you have to
Great summary, Betsy. I’d like to throw my support behind both an interactive option and a minimal option, as well as better tooling and doc
I think the primary pressure to rename app/javascript comes from when you’re doing SPA-style, you want Webpack for everything, and you don’t
I think it’s also fair for us to commit to the fact that Active Storage was specifically designed and intended to work with cloud storage se
Yeah, we don’t run the system tests, because they’re generally slow. We tend to primarily run system tests at Basecamp as a CI step. But thi
Just for a bit of history here. When we adopted Webpack as the preferred solution to compiling modern JavaScript in Rails, it was because We
Worth pointing out here is that the stuff we put in app/models/concerns are concerns that apply to multiple classes. An example from HEY is
I think we’d do well to explain concerns better. I’ve been writing code with mixins for so long that I’ve taken it completely for granted t