Avoiding ActiveRecord callbacks

my products:
typefast.gumro...
work with me:
www.typefast.c...

[@felipehansen4932]

Hey, liked your point of view, a question, what you think about using callbacks, but also using ActiveModel::Dirty methods, example: inside the callback function 'return unless self.api_key_changed? || self.username_changed?' or some related logic ?

[@swswisssw]

make a video where you will do the all process of installation ruby and rails on a Mac OS from scratch.

[@cocoarecords]

For real man!!! No gd explanation out there

[@codeline9387]

Thus, the active recording pattern is broken, the model can still become fat, it is better to move such code into service objects

[@jiachen1078]

Maybe we can try to use the intersect?(set)? e.g. `attributes.keys.to_set.intersect?([:user_name, :api_key, :jira_domain].to_set)`

[@ledockol]

Looks a little complicated)

[@ledockol]

(user.attributes.keys & ['extra', 'api_key', 'jira_domain']).any?

[@ranjansharma9990]

[:username, :api_key, :jira_domain].any? { |attr| attributes.keys.include?(attr) }