Comments (5)
There's no API for it yet, I'll try to add it in the upcoming, big 0.7.0 release, or 0.7.1
from dry-validation.
I'm going to make it possible to simply write key(:address, AddressSchema)
. Sounds good?
from dry-validation.
Would you expect AddressSchema
to be a Schema class or instance? Just wondering about how you'd go about composing schemas that need to be instantiated with dependencies provided for their own custom predicate methods to work...
from dry-validation.
@timriley I want to see if it's feasible to always use nested schemas, so that under each key you have a schema object and you can nest them, then schema rules would become a hash of nested schemas
from dry-validation.
immediate update: we can't assume a nested schema when using key
syntax because it could be either a nested hash or a flat value. So I'm wondering about either key(:foo, schema: true) { .. }
or schema(:foo) { .. }
. Hmm
from dry-validation.
Related Issues (20)
- Contract do not find schema keys defined with nested Dry Params. HOT 6
- Inconsistent behavior in nested schemas via passed in blocks HOT 8
- Incorrect validation of rule keys substring of schema keys
- Injecting dependencies using dry-auto_inject with reserved names
- `rule.each` produces error when input is `nil` HOT 2
- Building contract failed when or-ing types HOT 2
- Validation passes when array type is invalid HOT 1
- NoMethodError is raised when validating non-hash objects with a Dry::Validation::Contract that has config.validate_keys set to true HOT 4
- Dry::Validation::MissingMessageError after update dry stack HOT 2
- Weird issue since 1.10 dry-schema release HOT 3
- Validator didn't recognize nil string param value as empty, and didn't set default value HOT 6
- JSON schema contract failing to recognise valid input HOT 2
- Rule validation does not show in errors when the key validated is in an array of hashes HOT 1
- Mixing of `~>` and `<` in gemspec versioning HOT 1
- Documentation missmatch: `predicates_as_macros` is not available until v1.2
- `Dry::Validation::Result` lacks an `#output` method similar to `Dry::Schema::Result` HOT 4
- `Dry::Validation::Contract` behaves different when defined with a `params Dry::Schema::Params(parent: RawSchema)` vs. `params ParamsSchema` HOT 2
- errors(full: true), for nested input, could be better HOT 1
- False-positive when validating a nested datetime in an array of hashes HOT 2
- Consider release a new version with updated dependencies HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dry-validation.