-
Notifications
You must be signed in to change notification settings - Fork 88
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
Support YAML::Serializable #255
Support YAML::Serializable #255
Conversation
@Blacksmoke16 wow, very cool! |
An update on this, am going to skip adding docs for this for now. Plan on dealing with #223 by making a directory to split-up our README into one topic per file and will write up docs for YAML then. |
@Blacksmoke16 looks like this will need some manual intervention to bring up to date with the json stuff. |
rip. I'll take a look when i get home. EDIT: @robacarp They were simple, fixed it real quick. |
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.
thanks @Blacksmoke16
spec/granite_spec.cr
Outdated
describe "YAML" do | ||
context ".from_yaml" do | ||
it "can create an object from YAML" do | ||
yaml_str = %({"name": "yaml::anyReview","upvotes": 2, "sentiment": 1.23, "interest": 4.56, "published": 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.
should this be more classical yaml instead of basically json?
Thanks @Blacksmoke16 |
Surprise! Is branched off of #253 so needs that first.
I'll need to edit the README again, probably use same examples as the JSON, but say it could also be YAML.
EDIT: Since we didnt have this feature before i updated the labels.