[cordova-docs] 01/01: Testing a Plugin during development

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

janpio pushed a commit to branch janpio-test_plugin_development
in repository https://gitbox.apache.org/repos/asf/cordova-docs.git

commit ecefd700901c0a06855c387b7a7bf612ea968089
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Sat Apr 27 17:12:01 2019 +0200

    Testing a Plugin during development
---
 www/docs/en/dev/guide/hybrid/plugins/index.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/www/docs/en/dev/guide/hybrid/plugins/index.md b/www/docs/en/dev/guide/hybrid/plugins/index.md
index 92e26e1..070b079 100644
--- a/www/docs/en/dev/guide/hybrid/plugins/index.md
+++ b/www/docs/en/dev/guide/hybrid/plugins/index.md
@@ -185,6 +185,18 @@ listed below, and each builds on the simple Echo Plugin example above:
 - [iOS Plugins](../../platforms/ios/plugin.html)
 - [Windows Plugins](../../platforms/windows/plugin.html)
 
+## Testing a Plugin during development
+
+The simplest way to manually test a plugin during development is to create a 
+Cordova app as usual and add the plugin with the `--link` option:
+
+```bash
+cordova plugin add ../path/to/my/plugin/relative/to/project --link
+```
+
+This creates a symbolic link instead of copying the plugin files, which enables you 
+to work on your plugin and then simply rebuild the app to use your changes.
+
 ## Validating a Plugin using Plugman
 
 You can use the `plugman` utility to check whether the plugin installs


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org