-
Notifications
You must be signed in to change notification settings - Fork 34
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
CB-13342 : Updated README.md regarding package.json #27
Conversation
After reviewing the conversation from #24, I created this PR. Let me know if there's anything to change otherwise I can merge. @stevengill |
README.md
Outdated
@@ -62,6 +62,10 @@ Add a directory named `tests` to the root of your plugin. Within this directory, | |||
|
|||
For example, the `cordova-plugin-device` plugin has this nested [`plugin.xml`](https://github.com/apache/cordova-plugin-device/blob/master/tests/plugin.xml). | |||
|
|||
Create a `package.json` inside your project's `tests/` folder. The latest version of the tools ensure to run `npm install` on any plugin added to a project and pull in any dependencies. Therefore, plugin authors can now put npm dependencies around their tests into the `package.json` file. | |||
|
|||
For example,the `cordova-plugin-device` plugin contains a [`package.json`](https://github.com/apache/cordova-plugin-device/blob/736c7b9dfdfa25a924ffc3d1e409450633a8c00f/tests/package.json). |
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.
can you replace this link with the master version. https://github.com/apache/cordova-plugin-device/blob/master/tests/package.json
README.md
Outdated
@@ -62,6 +62,10 @@ Add a directory named `tests` to the root of your plugin. Within this directory, | |||
|
|||
For example, the `cordova-plugin-device` plugin has this nested [`plugin.xml`](https://github.com/apache/cordova-plugin-device/blob/master/tests/plugin.xml). | |||
|
|||
Create a `package.json` inside your project's `tests/` folder. The latest version of the tools ensure to run `npm install` on any plugin added to a project and pull in any dependencies. Therefore, plugin authors can now put npm dependencies around their tests into the `package.json` file. |
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.
Maybe before the second sentence, add a sentence about plugins requiring package.json
now and tests are considered their own plugins.
Thanks for the feedback- made the updates! Let me know if there's anything else! @stevengill |
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, Merge
Platforms affected
What does this PR do?
Updated README.md regarding package.json
What testing has been done on this change?
Checklist