You’re still going to want modules, npm, etc. Sprockets is never going to do all of that. All material apps need packaging. Webpacker is no
Happy to discuss all the concrete proposals on how to make things better. Right now Webpacker provides a out of the box experience where all
We mix data and sql statements in migrations all the time at Basecamp. This is what migrations were designed to do! They’re intended to be m
I’d go so far as to say that pending migrations should indeed just run by default in development and test, but those environments only. I’ve
What samsaffron said. We’re running HTTP/2 with HEY through nginx. The main benefit is higher concurrent loads and just a single HTTPS hands
You can hear the broader philosophy expanded in my RailsConf 2015 keynote as well: YouTube. Goes over the prepper’s backpack metaphor and mo
I really dislike that big error message as well. We should be able to catch the Pending Migrations Error and give it a dedicated page that s
I’ll give the short answer on the “what goes on the menu?” and it’s “the chef’s choice”. It’s not an empirical question with an empirical an
Like --auto-reboot and the reminder too! Totally agree that you can get away with a lot of magic when you tell people what tricks are being
I’d be happy to see #2. Having db:test:prepare always call db:seed isn’t going to fly. Too divergent use case. Totally fine for an individua
I’d be happy to see an easy way to slim down the formatting options available in Action Text. I’d even be interested in seeing a different t
Oh, and also ./bin/rails actionmailer:install along with all the other frameworks you can opt out off with --minimal or --interactive.
Betsy, I’m happy for us to start kicking off issues/PRs for some of these ideas. There’s a clear go-ahead on --minimal and --interactive 👍
Lol, that’s supposed to be “likely to be LOW-level”. That is infrastructure, not components.
The work we’d extract from HEY is likely to be high-level, like CurrentAttributes, has_secure_password, and the like. I don’t have any perso
TL6 isn’t timed with a specific Rails release for the moment, so when we’re ready to share the work, we can definitely do a bunch of joint d
Yes. The need for UJS is gone with TL6.
Oh, I hadn’t even realized that. Yes, I would support bringing back script/ as a default directory, and showing that this is a good usage.
I think it’s essentially the same approach: Detect code changes. Tell the user inline in the console: “The class MagicMonkey was changed.
I think we indeed have a muddy definition of seed that doesn’t actually fit the original strict view. Which makes it difficult to rely on it
Actually, the stale object point could be entirely sidestepped if instead of reload, we reboot. Simply start a brand new console session wit
Plan is to have TL6 out ~late summer/early fall. It’ll address this issue and more. TL6 is now fully aware of forms.
I think having an in-line notice that the code was changed, and to reload if you want those updates in the session, would be great. Doubt it
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