-
Notifications
You must be signed in to change notification settings - Fork 181
Schema #11
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
Conversation
!!value | ||
end | ||
end | ||
end |
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.
I wonder if field
should be a separate class but I cant think of any cases where its not more than a Struct
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.
I was keeping it within the Schemable namespace because you won't be creating one of these outside of this context.
I like it. Needs some documentation, though! |
…and 'true' should be cast to false and true
@justinweiss added some documentation in the README.md |
The README docs are good. Some of the methods in Schemable could use some short rdoc, though. |
Added some yard doc to Schemable and Schema |
Can define schema fields in your Client model