Chris Oliver

You can specify the column on your association that's used for joining tables. You'd just specify that old_id column and you should be good to go.

@Vitor the Apartment docs should have a good explanation for that. 👍

I would use a Stimulus controller to listen for "change" event on the radios and then update the hidden fields accordingly.

You can either:

1. Add some code to the model to transform the selected value here to what you want in the attributes before_validation
2. Add Javascript to change hidden fields based upon the selection

I'd probably go with Javascript personally in this case as I think it'd be a little simpler.

Seems like a perfect use case to me. You can add / remove options easily in the future without adding more migrations and that'll make maintaining the filter and options a lot easier.

You might look into some of the gems that enforce types on the options if you need to make sure things are cast to booleans, ints, etc.

Might just be a temporary issue on Wistia. It's not loading for me either.

Oh nice! I haven't made the upgrade quite yet.

Anything in particular you'd want to see? Mostly it operates the same as bash, just with a few niceties and you can use things like oh-my-zsh which I believe I talked about in this episode: https://gorails.com/episodes/my-development-environment-for-ruby-on-rails?autoplay=1

Mostly I just look at ruby-lang.org for the notes in the blog posts.

Strange. What does thr javascript console say for errors?

Try using the search icon in the navbar.

This would be a good one for the Rails github issue tracker.

I would bet they don't have that by default, but could probably be done by pasting the Rails source into your app, editing the toolbar for Trix, and then including your modified copy instead of the Rails JS for it.

ActionCable works great for this. Once the background job retrieves the data, you can have it send an updated partial over to the user and replace it on the page. I do this for server and app status updates on Hatchbox. Works great.

Awesome! I've got a long weekend out of town, but when I get back I can probably crank on a few episodes that start from the very basics.

I don't think there's any way to do this in the database with the current setup, so what you're doing is probably what I would do.

You could cache the results of the report and re-calculate them every day or week on a regular basis so you don't have to run this expensive calculation all the time.

I'd probably stick with what you've got.

haha! ive done that many times myself. Coding while tired doesnt work out very well.

Maybe a cool feature to add is checkboxes so you can see which steps youve completed!

You can run that code in the console by running the same code as you would in your app. response = Documents::CreateSession.new.start

The response will be the return value of start as it currently is setup.

The "Installing Ruby" step covers installing git, node, yarn, build essentials and the libssl, libreadline and zlib libraries. Sounds like you might have missed those steps.

Most of us prefer the Pundit gem for that. There's an episode on it as well. 👍

Not quite yet! I'm still working on it but keep getting distracted with other things. I'm hoping next week I can dedicated a lot of time to getting it all figured out and then re-record the course after that.

Moving a database isn't so easy. You typically incur downtime, or you have to setup streaming replicas and things that are complicated.