This morning I read “Integrated systems for integrated programmers” article by DHH. I totally agree with it, replacing a monolith by microservices won’t solve all its problems automagically.
Read more...Ruby on Rails
How we migrated from Timecop to built-in Rails 5.2 time helpers
Sooner or later each of us encounters a situation where a method depends on time. The feature needs to be tested later on. Among Rubyists, the most popular gem which provides handy helpers to this problem is called timecop. Since Ruby on Rails 5.2 it can be replaced by built-in methods defined within the ActiveSupport::Testing::TimeHelpers module.
Why don’t we validate controller parameters?
Using strong parameters in Ruby on Rails applications to allow permitted values is usually not enough. Taking care of validating allowed values to make our applications is also important to make them more secure and less error-prone. To handle the validation properly we can write custom solution(s) or use handy gems like apipie-rails.
Common mistakes that cause Ruby on Rails apps outages
Everybody makes mistakes. Some of them are caught early in a deployment pipeline: during writing code, testing it locally or code review process. Unfortunately, some hide cleverly and pop up on the production environment.
Read more...`ActiveSupport::ArrayInquirer` and even more Rails magic
In the previous article, we dived into ActiveSupport::StringInquirer class and superpowers it gives to String objects. After I had published that article I decided to take another look at the ActiveSupport module and to my surprise, I found something even more interesting, ActiveSupport::ArrayInquirer class.
`ActiveSupport::StringInquirer` magic
Rails magic is a widespread term among developers working with Ruby on Rails application. Is it an overstatement? Well, it depends.
Read more...5 security issues in Ruby on Rails apps from real life
…and how to fix them 🙂
Read more...