Skip to content

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

Merged
merged 9 commits into from
Aug 26, 2014
Merged

Schema #11

merged 9 commits into from
Aug 26, 2014

Conversation

chingor13
Copy link
Collaborator

Can define schema fields in your Client model

!!value
end
end
end

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

Copy link
Collaborator Author

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.

@justinweiss
Copy link

I like it. Needs some documentation, though!

@chingor13
Copy link
Collaborator Author

@justinweiss added some documentation in the README.md

@justinweiss
Copy link

The README docs are good. Some of the methods in Schemable could use some short rdoc, though.

@chingor13
Copy link
Collaborator Author

Added some yard doc to Schemable and Schema

chingor13 added a commit that referenced this pull request Aug 26, 2014
@chingor13 chingor13 merged commit 57d3bca into master Aug 26, 2014
@chingor13 chingor13 deleted the schema branch August 26, 2014 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants