apache
Some change requests for the "config.xml" page
Some change requests for the "config.xml" page:
content The description is duplicated and the attributes are not shown in a table.
access The description is duplicated and the attributes are not shown in a table. The "Whitelist Guide" link is not working.
allow-navigation The description is duplicated and the attributes are not shown in a table. There is a reference to the old cordova-plugin-whitelist
allow-intent The description is duplicated and the attributes are not shown in a table. There is a reference to the old cordova-plugin-whitelist
edit-config & config-file The links to edit-config & config-file for plugin.xml is not working.
AndroidInsecureFileModeEnabled file: is indicated once with three slashes and once with two slashes
KeepRunning The links to pause event is not working.
Sample config.xml There is a reference to the old cordova-plugin-whitelist
Min/Max Version The text shows the HTML "ul" and "li" tags
Thanks.
Hi @breautek
Most of these problems have been fixed in #1263
Now, to complete the solution of all the problems, some decisions remain to be made on the duplicate descriptions (for content, access, allow-navigation and allow-intent) and on the problem with Kramdown (see https://github.com/just-the-docs/just-the-docs/issues/409) that causes the lack of formatting of the lists in the second column with the descriptions of some attributes and the visualization of the HTML tags "ul" and "li" in the config.xml and plugin.xml pages
Attribute "Min/Max Version" in "preference" (in the config.xml page)
Attribute "name" in "engines and engine" (in the plugin.xml page)
Thanks.
Closing as completed based on original ticket request and title for config.xml.
The old markdown engine that Jekyll used to support could render HTML in the MD table. The current engine that Jekyll supports does not have this ability which created this issue.
All issues, for the most part, should have been resolved and would be in the dev docs, which will be the next release.
These issues will not be resolved for older docs. It will require manual triaging. It just depends on when anyone has time.
As for the plugin.xml, it is currently being investigated.
