Skip to content

Update intro.md #485

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update intro.md #485

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
baf10f8
Update intro.md
gtonussi May 28, 2025
c11f47e
Merge branch 'master' into patch-1
OutSystemsAMM May 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/integration-with-systems/mobile-plugins/cordova-plugin/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ Wrap a Cordova plugin through the **Extensibility Configuration** module propert
* the Cordova identifier (the value of the `identifier` key)
* the ZIP file from the **Resources** folder in the **Data** tab (the value of the `resource` key)

Unless it’s a [plugin supported by OutSystems](intro.md) and you're using a public repository to reference the plugin, it's recommended that you fork the plugin repository or use a tagged version, such as `https://example.com/sampleplugin/sampleplugin.git#1.1.0`. This prevents breaking changes in the plugin and the applications using the plugin. Additionally, if tags aren't used, two different builds may produce different results. This is important when deploying across one or more environments, where testing in one environment may be invalidated by a different build generated for another environment.
Unless it’s a [plugin supported by OutSystems](intro.md) and you're using a public repository to reference the plugin, it's recommended that you fork the plugin repository or use a tagged version, such as `https://example.com/sampleplugin/sampleplugin.git#v1.1.0`. This prevents breaking changes in the plugin and the applications using the plugin. Additionally, if tags aren't used, two different builds may produce different results. This is important when deploying across one or more environments, where testing in one environment may be invalidated by a different build generated for another environment.

You can use JSON for configuring additional settings required by the plugin. For detailed information about the description of the JSON, refer to [Extensibility Configurations JSON Schema](../../../deploying-apps/mobile-app-packaging-delivery/compliance-with-third-party-licenses.md).

Expand Down