The feature I'm more excited about is the multi DB support, you can finally easily setup a replica DB for reads and keep the writes in your main DB, with something like:
Parallel testing support is interesting and useful, it's a great way to see if your testing suite has issues (some suites have codependencies that are unknown until you run them in parallel :D). Aside from the possible speed improvements.
I was reading just yesterday about the new autoloader which would hopefully eliminate those weird cases when you still need a require statement here and there.
Glad they also upgraded minimum Ruby to 2.5.
I'll go through the various changelogs when I have a bit more time and report back 🤣
The feature I'm more excited about is the multi DB support, you can finally easily setup a replica DB for reads and keep the writes in your main DB, with something like:
(taken from github.com/rails/rails/pull/34052)
Parallel testing support is interesting and useful, it's a great way to see if your testing suite has issues (some suites have codependencies that are unknown until you run them in parallel :D). Aside from the possible speed improvements.
I was reading just yesterday about the new autoloader which would hopefully eliminate those weird cases when you still need a require statement here and there.
Glad they also upgraded minimum Ruby to 2.5.
I'll go through the various changelogs when I have a bit more time and report back 🤣
Fully agree on the parallel testing. It forces you to make independent tests.
I agree these are the most exciting.
I can't say I was dying for Action Text but I think we'd probably make use of it. Nice to have a "standard" of sorts for internal tools.
Action MailBox also a nice to have just in case.