Support "constant" keyword in Contract::Validate #187
Comments
|
That's a great idea! ❤️ |
|
😬 |
emaglio
added a commit
to emaglio/trailblazer-macro-contract
that referenced
this issue
Apr 8, 2018
…h Dry Schema Feature suggested by @swinner2 here: trailblazer/trailblazer#187 Validation using the Dry schema is triggered when the schema key is not nil. No checking on the object passed so if it is an actual Dry schema so it actually works with any callable object that returns an array of messages
emaglio
added a commit
to emaglio/trailblazer-macro-contract
that referenced
this issue
Apr 8, 2018
Feature suggested by @swinner2 here: trailblazer/trailblazer#187 Validation using the Dry schema is triggered when the key `schema` is not nil.
emaglio
added a commit
to emaglio/trailblazer-macro-contract
that referenced
this issue
Apr 9, 2018
Feature suggested by @swinner2 here: trailblazer/trailblazer#187 Validation using the Dry schema is triggered when the key `schema` is not nil.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
because Contract::Build is unnecessary when validating params against a dry-validation schema it would be nice to specify the schema constant in the Validate macro
step Contract::Validate( constant: CreateSchema )The text was updated successfully, but these errors were encountered: