Woohoo that's #Ruby 3.3!

Are We Ready For #Rails 7.1? Let's Find Out!

Now a real head-scratcher: "DEPRECATION WARNING: Passing instance variables to `render` is deprecated."

Not as many hits on th'internet as for other deprecation warnings I've run into.

I did find a blog post about it¹ but now I'm curious why I didn't see more warnings? (Could just be limited test coverage lol 🙈)

¹ https://andycroll.com/ruby/dont-use-instance-variables-in-partials/

Back in the saddle!

#Rails 7.1 seems to be working fine – I had to upgrade rspec-rails, which seemingly changed the behaviour of the "as" parameter… but, plot twist, I didn't need to have ever added that in the first place! 😳

Solved this one in 13 minutes on the subway home, actually kinda great conditions for it surprisingly?

A non-screen break and a walk to let my subconscious mull the problem for a bit.

Then, a short time limit and unreliable internet meant I had to skip the usual steps of "searching the error message" and "reading the online documentation" and go straight to the source code – which by now is mostly making sense.

Oh my days we're finally there!

#Ruby 3.3.9, #Rails 7.2 😎

Technically I could have stopped at #Rails 7.1 but it's only getting security updates another week.

And technically I could go to #Ruby 3.4 (3.3 is only supported another 6 months) and Rails 8 (7.2 is supported another 10 months)… but I need to start climbing out of this rabbit hole!

Firstly: test coverage. We're currently at around 40% (it's varied up and down about 3% between #Rails / #Ruby versions, which has been interesting!)

I'm not shooting for 100% – I've made the mistake before of making tests too brittle with respect to changes, and at the end of the day 100% lines covered doesn't necessarily mean 100% of functionality covered anyway.

But some of the key models and controllers are very minimally tested, which feels worth improving given the scale of the changes.

I'm also interested in setting up #Coveralls (maybe there are other similar services, but this is the only one that seems to have a Drone Plugin¹ for it already).

I'm not currently sure if if it makes sense to have coverage enforced by a CI step – but at least making this data more visible seems like a great start (and personally is helping the work I've done over the last week feel less abstract)

¹ https://plugins.drone.io/plugins/coveralls

I'm 90% sure that extending the test suite will smoke out other problems introduced by #Rails / #Ruby upgrades that I hadn't caught yet.

Of course, building a more comprehensive suite back on day 1 (Rails 4.2 😬) would have mitigated this – but I was really struggling with dependencies on such old versions of Ruby and Rails, keen to start making progress – and I was satisfied that 40% coverage was better-enough than 0% to get on with it.

After that, I want to focus on the #Docker image.

Somehow – despite applying a couple of Dockerfile tricks I've picked up since my last #Levelfly containerisation work back in 2021 – the image has ballooned from 400MB to 1.8GB, and I'd like to get that back down to size.

Part of this will likely involve publishing separate "development" and "production" images, to save new project contributors from a docker build process.

Woohoo, found my first bug thanks to extended #RSpec coverage 🥳

No luck getting #Simplecov to show me a list of uncovered methods yet, though 🤔

Search query "rails jobs worker"

🦆 Including results for railroad jobs employment

I mean, maybe?

Right, after some much-needed rest, Back 2 Levelfly

#Ruby #Rails