- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
ID: rails-best-practices/write-attribute
Language: Ruby
Severity: Notice
Category: Best Practices
This rule promotes the use of self
over the ActiveRecord method write_attribute
. This rule is important because using self
to assign attributes is more idiomatic in Ruby and leads to cleaner, more readable code.
The write_attribute
method in Rails is not recommended for regular use. It bypasses the normal attribute assignment process, skipping validations and callbacks. This can result in unexpected behavior and difficult-to-debug errors.
To avoid violating this rule, simply use self[:attribute] = value
instead of write_attribute(:attribute, value)
. For example, you can replace write_attribute(:price, 42)
with self[:price] = 42
.
class Product < ApplicationRecord
def price
write_attribute(:price, 42)
end
end
class Product < ApplicationRecord
def price
self(:price, 42)
end
end
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products