-
-
Notifications
You must be signed in to change notification settings - Fork 61
Adds default, and various properties related to minimum and maximum #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
| serde_json = "1.0" | ||
| serde_yaml = "0.7" | ||
| error-chain = "0.10" | ||
| serde_yaml = "0.8" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No particular reason for these two. Newer is better I'd hope
src/v2/schema.rs
Outdated
| fn from(item: PropertyDefault) -> Self { | ||
| match item { | ||
| PropertyDefault::Boolean(item) => item, | ||
| _ => true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about using rusts defaults for these i.e. returning Default::default()? I'm also wondering if there's a better way to communicate this wasn't the type you thought it was. I.e. if you're defererning a string default as a book ect
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I'm using Default::default() now.
I did not understand the second part of your comment
…riant of ParameterOrRef instead of copying the structure
Not ready to merge
I was testing with some files and most of they failed because of something missing. I've added just what I need. One step at a time!