-
Notifications
You must be signed in to change notification settings - Fork 17
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
Switch from schema to clojure.spec #106
Conversation
Whoa, this is awesome! I'll review in detail when I get a chance - hopefully later today. But at first glance looks like the right approach. |
@anthonygalea looks good so far! I noticed you renamed |
This is (I think) a minor improvement in naming with the aim of making things more readable. I typically like to work such changes piecemeal into commits as I encounter them. Having said that if such changes bug you let me know and I'll refrain from doing them. |
216de00
to
437c65f
Compare
Reviewed pull request, made additional changes and rebased on latest master. Also reviewed corresponding pull request in yetibot. |
Thanks for the explanation! I agree - I'm trying to figure out why the build is failing. It looks like the db schemas are empty at https://travis-ci.com/yetibot/yetibot.core/jobs/230115009#L250, so the database isn't being properly setup for test cases, which causes subsequent failures. |
437c65f
to
24265ba
Compare
Fixed, it was a bug in the spec for |
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.
Looks great overall - left a couple comments. Also wondering if we should use spec-alpha2 or wait to upgrade.
Differences are documented here but it's supposed to be mostly compatible. I need to read up more on the differences and what it'd look like. Can save it for a future PR if you want.
6b06b4e
to
d2e961f
Compare
Thanks a lot for your feedback @devth! Regarding spec2, thanks a lot for the link explaining the differences. I would prefer to tackle this in a future pull request if it's ok with you. |
Yep, sounds good! |
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.
Tested locally and everything looks good! @anthonygalea is this good to merge?
Great @devth. Yep good to merge. |
This is a first stab at migrating to clojure.spec. I wouldn't call it ready to be merged but thought it would be a good idea to get feedback early.