-
Notifications
You must be signed in to change notification settings - Fork 49
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
Node package and schema tests #15
Conversation
Fixes #7 |
Fixes #9 |
a3c4fae
to
6a5a41c
Compare
1bd77c1
to
23736fb
Compare
This removes 3 the extraneous console.warnings for each test file
23736fb
to
4241914
Compare
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.
LGTM with two questions.
package.json
Outdated
@@ -0,0 +1,20 @@ | |||
{ | |||
"name": "gamepad-mappings", |
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.
Color me surprised that this doesn't already exist, but even still I think something along the lines of "xr-gamepad-mappings" might be more appropriate?
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.
makes sense.... does that mean the repo name should be xr-gamepad-mappings?
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 don't know what npm etiquette is regarding that kind of thing, but probably?
package.json
Outdated
@@ -0,0 +1,20 @@ | |||
{ | |||
"name": "gamepad-mappings", | |||
"version": "1.0.0", |
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.
Is this at a functional-enough state to be considered version 1.0.0
? Don't really care what the version is, honestly, but people tend to think that "1.0" is a statement of stability/release-worthiness.
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.
Ah typo. I'll fix it. I meant to say 0.1.0
This PR replaces #4 and scopes the content down for ease of CR. It now only does two things: turns the repo into a node package and adds tests to validate the schema. It does not contain tests to validate the mapping files yet. That will come in a subsequent PR.
Ignore the changes to README.md; my next step is to fix up that file as part of PR #2 and I'll rebase on top once that's done.