SOLID Principles in Ruby on Rails
The article discusses the SOLID principles in the context of Ruby on Rails, emphasizing their importance in software design. It explains how Rails can make it easy to violate these principles, particularly through fat models and overloaded controllers. Each principle is illustrated with examples and suggested fixes to improve code maintainability and clarity.
- ▪SOLID is a set of five object-oriented design principles applicable to any programming language or framework.
- ▪The Single Responsibility Principle states that a class should have only one reason to change, which can be violated in Rails by having fat models.
- ▪The Open/Closed Principle suggests that classes should be open for extension but closed for modification to prevent breaking existing functionality.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3911796) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Shamila TP Posted on May 29 SOLID Principles in Ruby on Rails #rails #ruby #solidprinciples #softwaredevelopment SOLID Principles in Ruby on Rails SOLID is not a Rails or Ruby concept. It's a set of five object-oriented design principles that apply to any language/framework. But Rails makes it surprisingly easy to violate all five of them. Let's start with Single Responsibility Principle It states a class should have only one reason to change.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
