Skip to content
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

Update CONTRIBUTING.md #3873

Merged
merged 4 commits into from
May 29, 2017
Merged

Update CONTRIBUTING.md #3873

merged 4 commits into from
May 29, 2017

Conversation

flovilmart
Copy link
Contributor

No description provided.

@flovilmart flovilmart requested a review from acinader May 28, 2017 15:23
CONTRIBUTING.md Outdated

If your pull request introduces a change that may affect the storage or retrieval of objects, you may want to make sure it plays nice with Postgres.

* Run the tests against the postgres database with `PARSE_SERVER_TEST_DB=postgres npm test`. You'll need to have postgres running on your machine an setup [appropriatedly](https://github.com/parse-community/parse-server/blob/master/.travis.yml#L37)
Copy link
Contributor

Choose a reason for hiding this comment

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

machine an setup - misspelling.

CONTRIBUTING.md Outdated
If your pull request introduces a change that may affect the storage or retrieval of objects, you may want to make sure it plays nice with Postgres.

* Run the tests against the postgres database with `PARSE_SERVER_TEST_DB=postgres npm test`. You'll need to have postgres running on your machine an setup [appropriatedly](https://github.com/parse-community/parse-server/blob/master/.travis.yml#L37)
* If your feature is a mongoDB only feature and the test don't apply for a Postgres database, you can disable them with:
Copy link
Contributor

@vitaly-t vitaly-t May 28, 2017

Choose a reason for hiding this comment

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

If your feature is a mongoDB only feature and the test don't apply for a Postgres database, you can disable them with:

Incorrect English all the way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Suggestion?

Copy link
Contributor

Choose a reason for hiding this comment

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

Something like this -

If you only use MongoDB, you should disable PostgreSQL-specific tests with:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Or, if your feature is specific to MongoDB, ...

@codecov
Copy link

codecov bot commented May 28, 2017

Codecov Report

❗ No coverage uploaded for pull request base (master@38a525b). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #3873   +/-   ##
=========================================
  Coverage          ?   90.22%           
=========================================
  Files             ?      114           
  Lines             ?     7571           
  Branches          ?        0           
=========================================
  Hits              ?     6831           
  Misses            ?      740           
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 38a525b...dba0cc6. Read the comment docs.

@flovilmart flovilmart merged commit bd2ea87 into master May 29, 2017
@flovilmart flovilmart deleted the flovilmart-patch-1 branch May 29, 2017 00:36
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