RuboCop is the de facto standard for style-checking and code formatting in Ruby. It comes with lots of built-in rules (aka "cops") covering code style, metrics, naming, and many more. But did you know you can write your own cops, and make RuboCop even more useful than it already is?
The Rails community has always had a focus on testing and most Rails applications come with a decent to very solid test suite. However, most of the time, we developers focus on unit testing, integration testing, end-to-end testing... but how do we even make sure that our app will sustain the production load? Well, guess what: that can be tested too! ⚡️
In the development world, there are a few famous (endless) arguments: tabs or spaces? Windows or Linux? Vim or Emacs? And I could go on, and on. And well, the topic of this blog post could be added to the list: how do you handle non-RESTful actions in your controllers? Do you create custom actions, or do you try and stick to RESTful actions no matter what? Developers from "the Gnar company" have an opinion about this. (did the link title give it away?)
|