Skip to content

test: run draft-04/06 tests with ajv #169

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 4 commits into from
Mar 12, 2017
Merged

test: run draft-04/06 tests with ajv #169

merged 4 commits into from
Mar 12, 2017

Conversation

epoberezkin
Copy link
Member

@epoberezkin epoberezkin commented Mar 1, 2017

@Julian with this it runs the tests with both python and javascript, so draft-06 tests are tested and draft-04 are tested twice.

@handrews
Copy link
Contributor

handrews commented Mar 1, 2017

Looks good to me, although my JavaScript knowledge is very outdated. @tajo can you take a quick look? Ajv is the validator I was suggesting we use in doca as we move to Draft 06, btw.

Copy link
Member

@Julian Julian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine with me too (other than a minor note about the gitignore).

And by the way, I still can add support for the Python library as soon as we've published a meta schema somewhere permanent, so if we've done that, I'd be happy to as well.

.gitignore Outdated
@@ -1 +1,129 @@
TODO
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The intention here is that all this belongs in your global gitignore, since all this stuff should be ignored across all repos.

Copy link
Member Author

@epoberezkin epoberezkin Mar 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Julian so, just remove all this stuff from .gitignore then and leave it as TODO? Or am I missing something?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah exactly, unless there's anything specifically that needs ignoring in this repo, but not necessarily in all others.

(So for example, *.py[co] is not specific to this repo, those files should be ignored everywhere, in all repos. If you haven't seen it before by the way, my own global gitignore for example contains: https://github.com/Julian/dotfiles/blob/master/.config/git/ignore)

Copy link
Member Author

@epoberezkin epoberezkin Mar 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting. I usually just agree with whatever .gitignore GitHub creates (which is what I've added). In this way if people don't have a global one, they won't accidentally commit some wrong stuff. No problem though, I will remove. Should we at least keep ".tox" and "node_modules" there? They are created after running tests.

@epoberezkin
Copy link
Member Author

@Julian removed the change in .gitignore, if anything it should be a separate PR

@epoberezkin
Copy link
Member Author

@Julian is it ok to merge? I've updated to run draft-4/6 correctly.

@Julian
Copy link
Member

Julian commented Mar 12, 2017 via email

@epoberezkin epoberezkin merged commit 73a0593 into json-schema-org:master Mar 12, 2017
@epoberezkin epoberezkin deleted the draft6-tests-ajv branch March 12, 2017 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants