Great suggestion. I am waiting for it to hit RC1 before I do this episode. From my experience, things can change quite a bit during the Beta stages.

I’ve seen this one before. If i remember correctly, it was a fork of spree. Out of curiosity, any opinions of why you prefer this to spree?

I plan on covering VueJS in the future similar to how I did the ReactJS videos.

Unfortunately, time doesn't permit me to record multiple videos a week while maintaining the current quality. Once the Pro membership reaches a level where I can consider doing this full time, I will revisit the existing model.

This is such a heavy topic. It first starts with good code coverage! If your application has little or no code coverage, then there is no confidence that things are still working. Before making any major changes, whether it is refactoring or updating to a new Rails version, always make sure that you have adequate coverage.

It is a great topic to cover, but it will also greatly depend on the gems that are used for the application.  There are many gems out there that are slow to be maintained and they do not update for a later Rails support until a month or so after the Rails version has been released.

However, for a standard application with minimal gems used, we can definitely look at my process for updating the Rails version. I have a few tricks which may help mitigate headaches.

My guess would be when the type is saved to the database, it is being saved as Authority instead of Wobauth::Authority. Try adding a class_name to the association to see if that makes a difference. The users might be wobauth_users depending where it is declared.

has_many :users, class_name: 'Wobauth::Authority'