Well I need this feature because I have a problem when I trying to load these files.
let say if
Foo is loaded first than Zoo, then if I define like the standar way, it would be trigger an error that said Zoo is undefined or something because Zoo is not loaded yet, except I define require_relative 'zoo' on top of foo.rb file and I want to avoid this.
Is it possible to do? Thanks in advance
Adding require or require_relative for any other constants I need to refer to (like
Zoo in your case) to the top of my struct class files is exactly what I do in my apps.
require "dry/validation"
require "time_math"
schema = Dry::Validation.Schema do
configure do
def self.messages
super.merge(en: {errors: {ends_at_within_two_weeks_of_starts_at: 'must be within two weeks of start time'}})
end
end
required(:starts_at).filled(:time?)
required(:ends_at).filled(:time?)
validate(ends_at_within_two_weeks_of_starts_at: [:starts_at, :ends_at]) do |starts_at, ends_at|
two_weeks = 2 * 7 * 24 * 60
(ends_at - starts_at) <= two_weeks
end
end
valid_input = {
starts_at: TimeMath.day.decrease(Time.now, 10),
ends_at: Time.now,
}
schema.(valid_input).messages
# => {}
invalid_input = {
starts_at: TimeMath.day.decrease(Time.now, 20),
ends_at: Time.now,
}
schema.(invalid_input).messages
# => {:ends_at_within_two_weeks_of_starts_at=>["must be within two weeks of start time"]}
I did two weeks instead of two months, but you get the idea
i.e. I wouldn't need to to refer back to the dry-validation docs when writing them
Ah... i see you get free error-message-creation with high level rules
@timriley that makes sense and I agree. I guess it’s more of a convenience for the other developers. I wanted a generic schema to validate input for trailblazer operations that would whitelist and coerce, specifically
”true” => true. For now we’ll go with just whitelisting. Some people freak out when seeing types in ruby :scream_cat:
Hi, I'm trying to do something specific with
dry-validations, but am having a tough time. I have a field that needs to: 1. be optional 2. be an array, if it is present 3. have an each predicate run on the contents. It seems like chaining maybe(:array?).each(predicate) does not throw errors when the value is not an array.
What is the Dry::Types::Definition#try method for?
If so returns a
Success object with the value
If is not valid it will return
Failureobject with the value and the error message
But this doesn't?:
class SubForm < Form
define! do
required(:foo).filled(:int?)
optional(:bar).maybe(:int?)
end
end
class MainForm < Form
define! do
required(:qux).filled(:int?)
optional(:bar).maybe do
schema(SubForm) # Using class directly
end
end
end
