Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / MathiasPius/yaml-validator issues and pull requests
#42 - Allow publishing failures
Pull Request -
State: closed - Opened by MathiasPius about 1 year ago
#41 - Specify crate path in repo to hopefully not double-publish crates
Pull Request -
State: closed - Opened by MathiasPius about 1 year ago
#40 - Publish crates
Pull Request -
State: closed - Opened by MathiasPius about 1 year ago
#39 - yaml-validator and yaml-validator-cli crates on crates.io are out of date
Issue -
State: closed - Opened by debechu about 1 year ago
- 1 comment
#38 - Add binary release workflow
Pull Request -
State: closed - Opened by MathiasPius over 1 year ago
#37 - v0.1.1 binary release
Issue -
State: closed - Opened by circleous over 1 year ago
- 3 comments
#36 - Separate Schema and Validation errors.
Pull Request -
State: closed - Opened by MathiasPius almost 3 years ago
#35 - Refactor stale code to comply with cargo clippy
Pull Request -
State: closed - Opened by MathiasPius over 3 years ago
#34 - Boolean type validation
Pull Request -
State: closed - Opened by vkrinitsyn over 3 years ago
- 3 comments
#33 - Undo the appending of validation paths to the actual document paths.
Pull Request -
State: closed - Opened by MathiasPius almost 4 years ago
#32 - Split Schema and Document paths and communicate both in errors.
Issue -
State: open - Opened by MathiasPius almost 4 years ago
- 1 comment
#31 - Documentation improvements
Pull Request -
State: closed - Opened by MathiasPius almost 4 years ago
#30 - Update dependencies
Pull Request -
State: closed - Opened by MathiasPius almost 4 years ago
#29 - yaml-validator-cli should include samples and error tests using the new anyOf/oneOf/allOf schema
Issue -
State: open - Opened by MathiasPius almost 4 years ago
- 1 comment
#28 - Implement `TryFrom<&[Yaml]>` instead of TryFrom<&Vec<Yaml>> for Contexts
Pull Request -
State: closed - Opened by MathiasPius almost 4 years ago
#27 - Added better path information for failure states of oneOf and allOf.
Pull Request -
State: closed - Opened by MathiasPius almost 4 years ago
#26 - More accurate state paths for anyOf, allOf, oneOf.
Issue -
State: closed - Opened by MathiasPius about 4 years ago
#25 - Excessive code duplication in oneOf, anyOf, allOf.
Issue -
State: open - Opened by MathiasPius about 4 years ago
#24 - Implement modifiers
Pull Request -
State: closed - Opened by MathiasPius about 4 years ago
#23 - Simple typo-detection by matching MissingField with ExtraField
Issue -
State: open - Opened by MathiasPius over 4 years ago
- 1 comment
#22 - Contexts are consructed from Vec, but the Vec is immediately discarded.
Issue -
State: closed - Opened by MathiasPius over 4 years ago
#21 - Required keyword for objects
Pull Request -
State: closed - Opened by funkill over 4 years ago
- 1 comment
#20 - Consider turning the internal error field in SchemaErrorKind::ValidationError into a String.
Issue -
State: open - Opened by MathiasPius almost 5 years ago
#19 - SchemaErrorKind::MalformedField should use the path instead of an internal field.
Issue -
State: open - Opened by MathiasPius almost 5 years ago
#18 - Implement validation keywords for arrays
Pull Request -
State: closed - Opened by MathiasPius almost 5 years ago
#17 - Add validation keywords for numeric instances
Pull Request -
State: closed - Opened by MathiasPius almost 5 years ago
#16 - Implement 'not' subschema keyword
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement
#15 - Implement oneOf subschema keyword
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement
#14 - Implement anyOf subschema keyword
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement
#13 - Implement allOf subschema keyword
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement
#12 - Implement validation keywords for objects
Issue -
State: open - Opened by MathiasPius almost 5 years ago
Labels: enhancement
#11 - Implement validation keywords for arrays
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
Labels: enhancement
#10 - Implement validation keywords for strings
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
#9 - Implement validation keywords for numeric instances
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
Labels: enhancement
#8 - Figure out a way to test the library with --no-default-features
Issue -
State: open - Opened by MathiasPius almost 5 years ago
Labels: enhancement
#7 - Merge rewrite into master
Pull Request -
State: closed - Opened by MathiasPius almost 5 years ago
#6 - Add optional, but default SmallVec optimization for error paths
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
#5 - Using json-schema/OAS notation for write validation rules
Issue -
State: closed - Opened by funkill almost 5 years ago
- 3 comments
#4 - Implement 'strict' mode, which errors on objects containing more fields than specified in schema.
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement
#3 - Implement DataInteger/DataFloat types
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement
#2 - Remove 'key' component from dictionaries
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
#1 - Use yaml-rust directly to load documents
Issue -
State: closed - Opened by MathiasPius almost 5 years ago
- 1 comment
Labels: enhancement