Github user riknoll commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/461#discussion_r50564887
--- Diff: www/docs/en/dev/guide/platforms/android/lifecycle.md ---
@@ -80,14 +150,20 @@ The payload for the `resume` event adheres to the
following format:
{
action: "resume",
pendingResult: {
- pluginServiceName: <name of the plugin e.g. "Camera">,
- pluginStatus: <description of the result's status (see below)>,
- result: <argument(s) that would have been given to the callback>
+ pluginServiceName: string,
+ pluginStatus: string,
+ result: any
}
}
```
-The possible plugin statuses in the `pendingResult` field include the
following values:
+The fields of that payload are defined as follows:
+
+* `pluginServiceName`: The name of the plugin return the result (e.g.
"Camera"). This can be found in a plugin's plugin.xml
+* `pluginStatus`: The status of the plugin call (see below)
+* `result`: Whatever the result of the plugin call is
+
+The possible values for `pluginStatus` in the `pendingResult` field
include the following:
--- End diff --
There is no real reason it is a string vs an enum. I tried to clarify below
that the meaning of statuses are for the most part determined by the author of
the plugin. The other ones (class not found, etc.) are really intended for
plugin developers and don't really make sense to expose to the user. However,
we don't really have a choice in exposing them thanks to how cordova-android
handles plugin results. I will try and define them here, but I think plugin
developers should be the ones to specify what to check for.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
