-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
fix(contributing): minor corrections #201
Conversation
scripts/dev | ||
createdb postgraphql | ||
scripts/run-kitchen-sink-sql postgraphql | ||
scripts/dev -c pg://localhost/postgraphql |
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 felt uncomfortable installing schemas straight into the users default database; I can edit these changes back out if you prefer.
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.
How about we add a note instead that this is a valid alternative? Something like:
This will put the schemas into your default database. If you would prefer to put the schemas in another database pass a connection argument like so:
createdb postgraphql
scripts/run-kitchen-sink-sql postgres://localhost:5432/postgraphql
scripts/dev -c postgres://localhost:5432/postgraphql
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.
Ahhh! I was wondering why psql wasn't accepting the URL as an argument, didn't realise it needed postgres://
rather than pg://
@@ -40,7 +41,7 @@ scripts/test --watch | |||
Now, only the tests in the files you have changed will be run. There are some slow tests in the PostGraphQL suite so hopefully this should make your development time faster. Once you are in watch mode, Jest will present you with some options you can use to better configure your testing experience. | |||
|
|||
### Snapshots | |||
PostGraphQL makes use of the Jest snapshot feature. Even when you change small things in PostGraphQL the snapshot tests are likely to fail. This is OK, the snapshot tests are expected to fail. To make the snapshot tests pass again, run `scripts/test --watch` and then press `u` once the initial tests have run. Or run `scripts/test --updateSnapshot`. This will rerun the tests and changing the snapshot files in the repository. Commit the changes to the snapshots and the changed snapshots will be reviewed along with the rest of your changes in the PR review process. | |||
PostGraphQL makes use of the Jest snapshot feature. Even when you change small things in PostGraphQL the snapshot tests are likely to fail. This is OK, the snapshot tests are expected to fail. To make the snapshot tests pass again, run `scripts/test --watch` and then press `u` once the initial tests have run. Or run `scripts/test --updateSnapshot`. This will rerun the tests and change the snapshot files in the repository. Commit the changes to the snapshots and the changed snapshots will be reviewed along with the rest of your changes in the PR review process. |
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.
Not sure why GitHub hasn't highlit it, but I changed the word "changing" to "change"
4289958
to
14266fe
Compare
@calebmer Changes made 👍 |
Awesome looks good 👍 |
* First test * Add directives * Skipping fields/fragments based on directives
@calebmer I made these tweaks following your early merge of #197 (thanks for doing that!)
By the way, the
Types.money
tests are still failing for me; still haven't had a chance to dig in and figure out why. All the other tests are running well now though, thanks to the increased timeouts.