which I actually copied from sequel-rails railite
but it won’t be like that for long
because I’ll be adding proper support for instrumentation to rom and rom-sql (as I mentioned already)
@timriley I update dry view in the project and everything work ok (but will probably change few things after I see how you guys resolve it in berg, I'm not fully happy how I extend view_context by assets and current user . Plus I spend some time investigating why my partial do not work (single one) and found that it have the same name as one method in context. So it render method not partial, It's something a lot probably hit one day, so maybe another idea here will be better to explicity know when I want to render partial and when method
@solnic I think your last update for dry-web-(roda) can cause problems - (need changes in dry-web-roda). It requires log directory to exists for any app in apps folder, store logs there not in main log directory, plus app generator for dry-web-roda already add to boot logger and register it as logger in Container so it crash . Maybe it's only my app but worth to check
I’ll add docs over the weekend while flying to AU :laughing:
btw we follow “shifted semver” so if you see a minor bump while we’re still in beta (and all dry gems are in beta) then it means a breaking change
and re logger, just configure
config.logger = YourMainContainer[:logger] in sub-apps
unless you want separate loggers per app
we’re going to London first, spending the night, then jumping on a plane on Saturday again
I’m trying to create a custom form validation. I got the validation part working but not sure how to customize the coercion part automatically. Here’s what I have so far:
schema = Dry::Validation.Form do
configure do
def future_date?(value)
Date.new < Date.parse(value)
end
end
required(:date).filled(:future_date?)
end
@solnic but say i needed to coerce to some custom object,
MyCustomObj. is this easily possible too?
explicit type specs will be default API in 1.0.0 btw
@solnic thx for link i will reread that part. one more quick question is there a quick way to define error messages without going through a custom yaml file? eg, in this case i only need to define a single error message for this one custom
future_date? method and i’d prefer to define it in code near where future_date itself is defined
I guess we should document this
@solnic I’m getting an uninitialized constanct Messages error:
schema = Dry::Validation.Form do
configure do
def future_date?(value)
Date.today < value
end
def self.messages
Messages.default.merge(
en: { errors: { future_date?: 'Date must be in the future' } }
)
end
end
required(:date).filled(:date?, :future_date?)
end
i thought it was because i was in
Form instead of Schema but Schema isn’t working for me either...
@solnic finally got it working. not sure if it’s the best way or why the way in your spec didn’t work for me, but the following works:
schema = Dry::Validation.Form do
configure do
def future_date?(value)
Date.today < value
end
def self.messages
default_messages.merge(
en: { errors: { future_date?: 'Date must be in the future' } }
)
end
end
required(:date).filled(:date?, :future_date?)
end
which is probably a stupid idea