“Ruby’s dying, man”, they keep telling me. “Besides, it’s OOP, and that’s so 2013, functional programming is all the rage now. Oh, and there’s this new kid on the blog, it’s called Elixir. It’s functional programming for the avid Rubyist!”
Last time we built an authentication mechanism with a pretty glaring bug - you can just set the token in localStorage to whatever and it’ll let you in. We need to actually read the token, and persist what we’ve read so we don’t have to do it over and over.
In this part we’ll allow the user to log in to our frontend app, using the auth mechanism we’ve built on the back end earlier. A lot of topics in this one, so jump right in!
Now that we have our environment running, the app is initialized, and we know a little bit about what’s going on in there, it’s time to take a little bit of time to design our front end.
In this final part of our Rails API app series we’ll talk about specs, code coverage, continuous integration and deployment - and how to be certain your application is working.
