dry-bot on master
[devtools] sync (compare)
flash-gordon on master
It's 2021 everyone! (compare)
flash-gordon on v1.5.0
dry-bot on master
[devtools] sync (compare)
flash-gordon on master
Set release date (compare)
flash-gordon on master
Add docs for fallbacks and cust… (compare)
dry-bot on master
[devtools] sync (compare)
flash-gordon on master
Update changelog.yml (compare)
input_value.included_in?(list)
vs input_value.includes?(value)
One more thing provided by @marshall-lee for initializer in our commercial project is the ar_param
or ar_option
.
It allows to set object dependency as either model or model id.
In Rails projects this proves to be very suitable (example below is over-simplified):
class DestroyUser
ar_param :user
def call
user.destroy
end
def self.call(*args)
new(*args).call
end
end
user_id = 1
user = User.find 1
# This methods are the same
DestroyUser.call user_id
DestroyUser.call user
Under the hood the method either gets an activerecord instance or finds its by id (or by another argument):
ar_param :user, find_by: :key
The question is what do you think about implementing this behaviour in a submodule of dry-initializer
(dry-initializer/rails
)?
[17] pry(main)> LocalSearch::Types::Form::Bool['1']
=> true
[18] pry(main)> LocalSearch::Types::Form::Bool['0']
=> false
[19] pry(main)> LocalSearch::Types::Form::Bool['false']
=> false
[20] pry(main)> LocalSearch::Types::Form::Bool['False']
=> "False"