Chris Oliver

Yeah I was gonna say, no sense in fiddling with this if what you got works. :P

I'll have to check out loading CSS with webpack sometime soon and see how that all works. This stuff is an absolute mess. I hope that it gets more sane in the next few months.

Yeah, I figured it wouldn't work automatically like that. I'm not used to using webpack with SCSS, so it's new to me.

From a random Github issue, it looks like maybe adding a tilde at the beginning would work? @import "~bulma/bulma/utilities/utilities";

You can actually use yarn now to add packages which is a little better than using npm now. yarn add bulma will do the same thing as above and it makes things easier.

One thing I will say is I think that you shouldn't have to specify the node_modules folder at all. That should be available in the path I would assume. You should be able to do something like this instead: @import "bulma/sass/utilities/initial-variables"

Yeah, I was going to suggest the geocoder gem. It's probably the only one I've used over the last few years and it works rather well. Documentation isn't super duper great, but it's not bad.

Let me know if you have any questions on it!

Yeah, some interesting changes in how forms work by default. I was disappointed to see that scaffolds don't submit forms with AJAX as that seems like one of the obvious places for them to change and show you how to submit and handle errors.

I'm planning on doing a deeper dive into Rails UJS to see all the new features soon. Seems like a lot has changed instead of it just being a direct port to remove jQuery like I thought it was supposed to.

You can actually use rails form tags and put your vue element inside it and on submit, look up to the form for the url, the method, and csrf token.

The reason I didn't do that here is because the new Rails UJS library was throwing some JS errors for me because it was intercepting the button clicks inside the form. I didn't have time to figure that out so I just removed the form and did it manually. Meant to mention that in the video as that's the way I would ideally set it up.

Well you wouldn't because it's up to your Javascript to generate the views dynamically. You would just cache the JSON response server side and the browser will generate the html from scratch every time.

Mostly the reason why AMS is used over jBuilder is that it's agnostic from the format. You can choose to output AMS in different formats using different adapters like the JSON API adapter. This means you can define the attributes and relationships of your data that you want to export, but you don't have to match that exactly with the JSON format. It becomes more interchangeable that way and you can make modifications a bit easier.

jBuilder is a lot more manual building out the exact structure of the JSON which makes it a bit harder to work with generally.

You've just got to download the backup, extract it, and reimport your database and do the same for whatever else you may have backed up.

Interesting, so that would mean that your filter is likely the piece that's not working correctly. You may want to also console.log tree so that you can see what that string is and verify that filter is working. I'd guess there's something up with that.

Hey Aaron,

What exactly is it that isn't working correctly? You said that it logs things in the console correctly, which I assume means that every time you change the first select, you always get it to log the correct options for the second one?

If those are the right options being printed from the second console.log in the change event, then maybe the problem is just the html call to replace the options?

I didn't have time to get into that at all. One thing is that if you have a database unique index, then the database won't accept duplicate numbers which is good. You would probably want to add a "retry" in so that you could increment again and try that number maybe a few times.

This is sort of related, but I did a couple episodes on Docusign.

https://gorails.com/episodes/electronic-signatures-with-the-docusign-api
https://gorails.com/episodes/docusign-webhooks-ngrok

Go right ahead. :D

I will try doing that! I've gotta get my Windows 10 install back working again. :S

Sorta useful but if we wanted a simple increment always we could just use the database for that. Since we have more logic like years restart the count (or the numbers could be not successive in a lot of cases) that won't help in every case.

Always great to use those little ruby niceties when you can though! Thanks for the reminder!

Either one would be great or JS samples even!

This is fantastic, keep hustling on it! :D Having more native screencasts is going to help so much!

Great work detective! :D

Yep, and just for reference I use a 2GB server for it, but was on a 1GB server for a long time.