[jira] [Commented] (CB-13944) Why isn't the "platforms" documentation not the README of the platform repositories and pulled into the docs?
[ https://issues.apache.org/jira/browse/CB-13944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383986#comment-16383986 ] Dmitry Blotsky commented on CB-13944: - This sounds like a good idea. I'd say it's not a Bug though. This is more like an Improvement. > Why isn't the "platforms" documentation not the README of the platform > repositories and pulled into the docs? > - > > Key: CB-13944 > URL: https://issues.apache.org/jira/browse/CB-13944 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > The version of the platform that is installed is hard coded in the CLI. > Wouldn't it make sense to move the "platform" documentation to the README of > the platform itself and only pull in this file (like the docs already do with > plugins) so there is some connection to the actual version? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13935) Possible 404 in ToC
[
https://issues.apache.org/jira/browse/CB-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384002#comment-16384002
]
Dmitry Blotsky commented on CB-13935:
-
[~Sujan12] what's causing this is right in the message: there is a possible 404
at that location in the ToC. That is, the ToC for docs/de/6.x references this
file, but it doesn't exist. This is because the file is missing in the source
tree. To fix it, you either need to remove it from the ToC, or create the file.
> Possible 404 in ToC
> ---
>
> Key: CB-13935
> URL: https://issues.apache.org/jira/browse/CB-13935
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-docs
>Reporter: Jan Piotrowski (Sujan)
>Priority: Major
>
> The build process of cordova-docs is full with these:
> {code}
> WARNING! Possible 404 in ToC: "www/docs/de/6.x/guide/platforms/osx/index.md";
> create the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-cli/index.md"; create the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-battery-status/index.md"; create
> the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-camera/index.md"; create the file
> to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-console/index.md"; create the file
> to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-contacts/index.md"; create the file
> to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-device/index.md"; create the file
> to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-device-motion/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-device-orientation/index.md";
> create the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-dialogs/index.md"; create the file
> to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-file/index.md"; create the file to
> fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-file-transfer/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-geolocation/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-globalization/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-inappbrowser/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-media/index.md"; create the file to
> fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-media-capture/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-network-information/index.md";
> create the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-splashscreen/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-vibration/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-statusbar/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-whitelist/index.md"; create the
> file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/6.x/reference/cordova-plugin-legacy-whitelist/index.md"; create
> the file to fix
> WARNING! Possible 404 in ToC: "www/docs/de/7.x/guide/platforms/osx/index.md";
> create the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/7.x/reference/cordova-cli/index.md"; create the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/7.x/reference/cordova-plugin-battery-status/index.md"; create
> the file to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/7.x/reference/cordova-plugin-camera/index.md"; create the file
> to fix
> WARNING! Possible 404 in ToC:
> "www/docs/de/7.x/reference/cordova-plugin-console/index.md"; create the file
> to fix
> {code}
> We should probably find out what is causing this and fix it somehow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13944) Why isn't the "platforms" documentation not the README of the platform repositories and pulled into the docs?
[ https://issues.apache.org/jira/browse/CB-13944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384094#comment-16384094 ] Jan Piotrowski (Sujan) commented on CB-13944: - Changed. One challenge would be to collect all platform information (some may have more than one page currently), and merge it with the current README. > Why isn't the "platforms" documentation not the README of the platform > repositories and pulled into the docs? > - > > Key: CB-13944 > URL: https://issues.apache.org/jira/browse/CB-13944 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > The version of the platform that is installed is hard coded in the CLI. > Wouldn't it make sense to move the "platform" documentation to the README of > the platform itself and only pull in this file (like the docs already do with > plugins) so there is some connection to the actual version? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13941) Why should Plugin APIs be included in the docs?
[ https://issues.apache.org/jira/browse/CB-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) updated CB-13941: Issue Type: Improvement (was: Bug) > Why should Plugin APIs be included in the docs? > --- > > Key: CB-13941 > URL: https://issues.apache.org/jira/browse/CB-13941 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > What is the use of copying the plugin documentation over to the website? > These are is always less current than the actual GitHub README itself and > also has strange effects on both sides (Frontmatter on GitHub, outdated > README without version info in old Cordova docs, strange badge tables in > Cordova docs). > Having a list of Core Plugins with links to the actual documentation of them > of course makes total sense and could replace the copied over READMEs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13940) / vs. /index.html
[ https://issues.apache.org/jira/browse/CB-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384092#comment-16384092 ] Jan Piotrowski (Sujan) commented on CB-13940: - Internal consistency and SEO - no need to link to 2 different URLs internally if you control the site generation. > / vs. /index.html > - > > Key: CB-13940 > URL: https://issues.apache.org/jira/browse/CB-13940 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > Right now the docs are a mishmash of linking to `folder/` and > `folder/index.html`. > http://cordova.apache.org/docs/en/dev/guide/appdev/privacy/index.html > http://cordova.apache.org/docs/en/dev/guide/appdev/privacy/ > http://cordova.apache.org/docs/en/dev/reference/cordova-plugin-dialogs/index.html > http://cordova.apache.org/docs/en/dev/reference/cordova-plugin-dialogs/ > Both are of course totally valid - we just have to standardize on one and use > it everywhere, if possible also create a redirect rule for all "broken" links > to use the one standard we define. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13946) How to deal with pages that are missing in this new version of the docs?
[ https://issues.apache.org/jira/browse/CB-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384083#comment-16384083 ] Jan Piotrowski (Sujan) commented on CB-13946: - Oh right, checking `https://github.com/apache/cordova-docs/blob/master/www/_data/redirects.yml` shows there are redirects in place. Wouldn't it make sense to fix these links in `dev` source though? > How to deal with pages that are missing in this new version of the docs? > > > Key: CB-13946 > URL: https://issues.apache.org/jira/browse/CB-13946 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > There are multiple broken links in the `dev` version of the docs that link to > pages that used to be there but are not in the current version. > Examples: > - /docs/en/dev/guide/platforms/ios/upgrade.html links to > /docs/en/dev/guide/platforms/ios/tools.html in multiple places > - /docs/en/dev/guide/platforms/windows/index.html (used to be > /docs/en/dev/guide/platforms/win8/index.html) links to > /docs/en/dev/guide/platforms/wp8/index.html > How can and should those be handled? > The content still exists, but in older versions :/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13940) / vs. /index.html
[ https://issues.apache.org/jira/browse/CB-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383996#comment-16383996 ] Dmitry Blotsky commented on CB-13940: - Both will always be accessible. This is done by almost all sites. For example, https://www.facebook.com/index.php and https://www.facebook.com/ both work. Do you mean that internal links should stick to one? If so, why do you feel this change is necessary? > / vs. /index.html > - > > Key: CB-13940 > URL: https://issues.apache.org/jira/browse/CB-13940 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > Right now the docs are a mishmash of linking to `folder/` and > `folder/index.html`. > http://cordova.apache.org/docs/en/dev/guide/appdev/privacy/index.html > http://cordova.apache.org/docs/en/dev/guide/appdev/privacy/ > http://cordova.apache.org/docs/en/dev/reference/cordova-plugin-dialogs/index.html > http://cordova.apache.org/docs/en/dev/reference/cordova-plugin-dialogs/ > Both are of course totally valid - we just have to standardize on one and use > it everywhere, if possible also create a redirect rule for all "broken" links > to use the one standard we define. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13945) `npm test` still relevant?
[
https://issues.apache.org/jira/browse/CB-13945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383999#comment-16383999
]
Dmitry Blotsky commented on CB-13945:
-
Yes. This was part of the previous docs generator, written by [~akurdyumov].
Some of the files are still helpful, and some have been replaced. We can sit
down and look through these, to see what to keep.
> `npm test` still relevant?
> --
>
> Key: CB-13945
> URL: https://issues.apache.org/jira/browse/CB-13945
> Project: Apache Cordova
> Issue Type: Task
> Components: cordova-docs
>Reporter: Jan Piotrowski (Sujan)
>Priority: Major
>
> There are some tests in cordova-docs which can be run with `npm test`,
> described here:
> https://github.com/apache/cordova-docs/blob/master/doc/testing-the-website.md
> {code}
> C:\Projects\Cordova\cordova-docs (janpio-random_docs_stuff -> origin)
> (cordova-website@0.0.1)
> λ npm test
> > cordova-website@0.0.1 test C:\Projects\Cordova\cordova-docs
> > npm run eslint && npm run mocha
> > cordova-website@0.0.1 eslint C:\Projects\Cordova\cordova-docs
> > eslint tools/lib tools/spec
> > cordova-website@0.0.1 mocha C:\Projects\Cordova\cordova-docs
> > mocha --recursive tools/spec
> (node:11372) [DEP0006] DeprecationWarning: child_process: options.customFds
> option is deprecated. Use options.stdio instead.
> AddTitle
> √ should set the title
> √ should skip files with no source title
> √ should skip files with no target title
> Prettify
> √ should find some code blocks
> √ should add the prettyprint class to each code block
> TableOfContents
> √ should find the table of content values
> √ should find all elements
> √ should find all elements
> √ should ignore whitespace in the target name
> √ should create a HTML select element
> √ should skip files with no source title
> √ should skip files with no target title
> UpdateIndex
> √ should skip all files but index.md.html
> √ should rename the title
> √ should rename the file
> UpdateKeywordIndex
> √ should skip all files but _index.html
> √ should rename the title
> √ should rename the h1 (66ms)
> √ should remove the
> √ should update references from index.md.html to index.html
> YamlFrontMatter
> √ should skip files with no YAML Front Matter
> √ should parse files with YAML Front Matter
> FileHelpers
> - should have a default input directory that exists
> 22 passing (901ms)
> 1 pending
> {code}
> If you follow the trail, this seems to run the tests in `tools/spec/cordova`.
> Looking into the actual spec files, it seems to test functionality in these
> files:
> - /lib/cordova/post/addtitle
> - /lib/cordova/post/prettify
> - /lib/cordova/post/tableofcontents
> - /lib/cordova/post/updateindex
> - /lib/cordova/post/updatekeywordindex
> - /lib/cordova/pre/yamlfrontmatter
> Is the code being tested here actually still relevant for the current state
> of the docs?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13946) How to deal with pages that are missing in this new version of the docs?
[ https://issues.apache.org/jira/browse/CB-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383982#comment-16383982 ] Dmitry Blotsky commented on CB-13946: - [~Sujan12] this works on the live site. There is a redirect for this page. To test redirects locally, you need to serve the built site with the Apache HTTP server. > How to deal with pages that are missing in this new version of the docs? > > > Key: CB-13946 > URL: https://issues.apache.org/jira/browse/CB-13946 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > There are multiple broken links in the `dev` version of the docs that link to > pages that used to be there but are not in the current version. > Examples: > - /docs/en/dev/guide/platforms/ios/upgrade.html links to > /docs/en/dev/guide/platforms/ios/tools.html in multiple places > - /docs/en/dev/guide/platforms/windows/index.html (used to be > /docs/en/dev/guide/platforms/win8/index.html) links to > /docs/en/dev/guide/platforms/wp8/index.html > How can and should those be handled? > The content still exists, but in older versions :/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13941) Why should Plugin APIs be included in the docs?
[ https://issues.apache.org/jira/browse/CB-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383992#comment-16383992 ] Dmitry Blotsky commented on CB-13941: - I believe this was done for convenience: it's nice to have the plugin docs be part of the whole site, and be styled the same way. This way also the site search can index them, and we capture plugin docs for older versions (at least mostly correctly). Also, this sounds like an Improvement or a Feature, not a Bug. > Why should Plugin APIs be included in the docs? > --- > > Key: CB-13941 > URL: https://issues.apache.org/jira/browse/CB-13941 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > What is the use of copying the plugin documentation over to the website? > These are is always less current than the actual GitHub README itself and > also has strange effects on both sides (Frontmatter on GitHub, outdated > README without version info in old Cordova docs, strange badge tables in > Cordova docs). > Having a list of Core Plugins with links to the actual documentation of them > of course makes total sense and could replace the copied over READMEs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13944) Why isn't the "platforms" documentation not the README of the platform repositories and pulled into the docs?
[ https://issues.apache.org/jira/browse/CB-13944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) updated CB-13944: Issue Type: Improvement (was: Bug) > Why isn't the "platforms" documentation not the README of the platform > repositories and pulled into the docs? > - > > Key: CB-13944 > URL: https://issues.apache.org/jira/browse/CB-13944 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > The version of the platform that is installed is hard coded in the CLI. > Wouldn't it make sense to move the "platform" documentation to the README of > the platform itself and only pull in this file (like the docs already do with > plugins) so there is some connection to the actual version? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13939) Privacy Guide has 4 broken links
[ https://issues.apache.org/jira/browse/CB-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) updated CB-13939: Description: > See the following documentation pages for more information: camera, capture, > contacts, and geolocation. All 4 links are broken. was: > See the following documentation pages for more information: camera, capture, > contacts, and geolocation. All 4 links are borken. > Privacy Guide has 4 broken links > > > Key: CB-13939 > URL: https://issues.apache.org/jira/browse/CB-13939 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > > See the following documentation pages for more information: camera, > > capture, contacts, and geolocation. > All 4 links are broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13946) How to deal with pages that are missing in this new version of the docs?
Jan Piotrowski (Sujan) created CB-13946: --- Summary: How to deal with pages that are missing in this new version of the docs? Key: CB-13946 URL: https://issues.apache.org/jira/browse/CB-13946 Project: Apache Cordova Issue Type: Improvement Components: cordova-docs Reporter: Jan Piotrowski (Sujan) There are multiple broken links in the `dev` version of the docs that link to pages that used to be there but are not in the current version. Examples: - /docs/en/dev/guide/platforms/ios/upgrade.html links to /docs/en/dev/guide/platforms/ios/tools.html in multiple places - /docs/en/dev/guide/platforms/windows/index.html (used to be /docs/en/dev/guide/platforms/win8/index.html) links to /docs/en/dev/guide/platforms/wp8/index.html How can and should those be handled? The content still exists, but in older versions :/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13931) Remove translations from cordova docs site
[ https://issues.apache.org/jira/browse/CB-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383645#comment-16383645 ] Jan Piotrowski (Sujan) commented on CB-13931: - Those above are notes on tasks and topics to be thought and talked about, not decisions what should or will be done. Discussion on what or not what to do should probably happen in the dev mailing list. > Remove translations from cordova docs site > -- > > Key: CB-13931 > URL: https://issues.apache.org/jira/browse/CB-13931 > Project: Apache Cordova > Issue Type: Task > Components: cordova-docs >Reporter: Steve Gill >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13944) Why isn't the "platforms" documentation not the README of the platform repositories and pulled into the docs?
[ https://issues.apache.org/jira/browse/CB-13944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) updated CB-13944: Description: The version of the platform that is installed is hard coded in the CLI. Wouldn't it make sense to move the "platform" documentation to the README of the platform itself and only pull in this file (like the docs already do with plugins) so there is some connection to the actual version? > Why isn't the "platforms" documentation not the README of the platform > repositories and pulled into the docs? > - > > Key: CB-13944 > URL: https://issues.apache.org/jira/browse/CB-13944 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Priority: Major > > The version of the platform that is installed is hard coded in the CLI. > Wouldn't it make sense to move the "platform" documentation to the README of > the platform itself and only pull in this file (like the docs already do with > plugins) so there is some connection to the actual version? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13356) `windows` platform has misleading `win8` in URIs
[ https://issues.apache.org/jira/browse/CB-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383588#comment-16383588 ] ASF subversion and git services commented on CB-13356: -- Commit a0a7f14323b28c05b2248348a736eb1645d94dfb in cordova-docs's branch refs/heads/master from Jan Piotrowski [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=a0a7f14 ] CB-13356 Rename `win8` to `windows` (#797) CB-13356 Rename `win8` to `windows` > `windows` platform has misleading `win8` in URIs > > > Key: CB-13356 > URL: https://issues.apache.org/jira/browse/CB-13356 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) >Priority: Major > > URL of guide right now: > https://cordova.apache.org/docs/en/latest/guide/platforms/win8/index.html > `win8` might confuse people and should be replaced with `windows`. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13356) `windows` platform has misleading `win8` in URIs
[ https://issues.apache.org/jira/browse/CB-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383586#comment-16383586 ] ASF GitHub Bot commented on CB-13356: - janpio closed pull request #797: CB-13356 Rename `win8` to `windows` URL: https://github.com/apache/cordova-docs/pull/797 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > `windows` platform has misleading `win8` in URIs > > > Key: CB-13356 > URL: https://issues.apache.org/jira/browse/CB-13356 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) >Priority: Major > > URL of guide right now: > https://cordova.apache.org/docs/en/latest/guide/platforms/win8/index.html > `win8` might confuse people and should be replaced with `windows`. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13356) `windows` platform has misleading `win8` in URIs
[ https://issues.apache.org/jira/browse/CB-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383587#comment-16383587 ] ASF subversion and git services commented on CB-13356: -- Commit a0a7f14323b28c05b2248348a736eb1645d94dfb in cordova-docs's branch refs/heads/master from Jan Piotrowski [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=a0a7f14 ] CB-13356 Rename `win8` to `windows` (#797) CB-13356 Rename `win8` to `windows` > `windows` platform has misleading `win8` in URIs > > > Key: CB-13356 > URL: https://issues.apache.org/jira/browse/CB-13356 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) >Priority: Major > > URL of guide right now: > https://cordova.apache.org/docs/en/latest/guide/platforms/win8/index.html > `win8` might confuse people and should be replaced with `windows`. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13356) `windows` platform has misleading `win8` in URIs
[ https://issues.apache.org/jira/browse/CB-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) resolved CB-13356. - Resolution: Fixed merged > `windows` platform has misleading `win8` in URIs > > > Key: CB-13356 > URL: https://issues.apache.org/jira/browse/CB-13356 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) >Priority: Major > > URL of guide right now: > https://cordova.apache.org/docs/en/latest/guide/platforms/win8/index.html > `win8` might confuse people and should be replaced with `windows`. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13944) Why isn't the "platforms" documentation not the README of the platform repositories and pulled into the docs?
Jan Piotrowski (Sujan) created CB-13944: --- Summary: Why isn't the "platforms" documentation not the README of the platform repositories and pulled into the docs? Key: CB-13944 URL: https://issues.apache.org/jira/browse/CB-13944 Project: Apache Cordova Issue Type: Bug Components: cordova-docs Reporter: Jan Piotrowski (Sujan) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13943) ERR_FILE_NOT_FOUND
[ https://issues.apache.org/jira/browse/CB-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jcesarmobile updated CB-13943: -- Priority: Major (was: Critical) > ERR_FILE_NOT_FOUND > -- > > Key: CB-13943 > URL: https://issues.apache.org/jira/browse/CB-13943 > Project: Apache Cordova > Issue Type: Bug > Environment: Android — any > Cordova — 6.5.0 >Reporter: Arthur Mudrick >Priority: Major > Attachments: > Screenshot_2018-02-28-15-18-50-964_ru.balumates.balu.png, > Screenshot_2018-02-28-15-55-56-348_ru.balumates.balu.png > > > I use Angular with Cordova. Angular uses URL routing, e.g. `/login` for the > Login page, '/settings' for the Settings page, etc. > When Android application updates (when new application version is installed) > Cordova is like «reloads» itself or something, but the path in the address > bar was `/login` or `/users` or `/settings` etc., so, Cordova thinks it is a > folder. > Cordova throws an error — see screenshot #1 — there is a path `/www/users` > but the `/users` is just Angular's routing, not a folder to search for :) > I also tried to make Angular work with hashbang url strategy, e.g. `/#/login` > rather than `/login` — it throws another error, see screenshot #2. > So, basically Cordova behaves like a server without the `mod_rewrite` option > — it tries to find folders inside the `/www` folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13945) `npm test` still relevant?
Jan Piotrowski (Sujan) created CB-13945:
---
Summary: `npm test` still relevant?
Key: CB-13945
URL: https://issues.apache.org/jira/browse/CB-13945
Project: Apache Cordova
Issue Type: Task
Components: cordova-docs
Reporter: Jan Piotrowski (Sujan)
There are some tests in cordova-docs which can be run with `npm test`,
described here:
https://github.com/apache/cordova-docs/blob/master/doc/testing-the-website.md
{code}
C:\Projects\Cordova\cordova-docs (janpio-random_docs_stuff -> origin)
(cordova-website@0.0.1)
λ npm test
> cordova-website@0.0.1 test C:\Projects\Cordova\cordova-docs
> npm run eslint && npm run mocha
> cordova-website@0.0.1 eslint C:\Projects\Cordova\cordova-docs
> eslint tools/lib tools/spec
> cordova-website@0.0.1 mocha C:\Projects\Cordova\cordova-docs
> mocha --recursive tools/spec
(node:11372) [DEP0006] DeprecationWarning: child_process: options.customFds
option is deprecated. Use options.stdio instead.
AddTitle
√ should set the title
√ should skip files with no source title
√ should skip files with no target title
Prettify
√ should find some code blocks
√ should add the prettyprint class to each code block
TableOfContents
√ should find the table of content values
√ should find all elements
√ should find all elements
√ should ignore whitespace in the target name
√ should create a HTML select element
√ should skip files with no source title
√ should skip files with no target title
UpdateIndex
√ should skip all files but index.md.html
√ should rename the title
√ should rename the file
UpdateKeywordIndex
√ should skip all files but _index.html
√ should rename the title
√ should rename the h1 (66ms)
√ should remove the
√ should update references from index.md.html to index.html
YamlFrontMatter
√ should skip files with no YAML Front Matter
√ should parse files with YAML Front Matter
FileHelpers
- should have a default input directory that exists
22 passing (901ms)
1 pending
{code}
If you follow the trail, this seems to run the tests in `tools/spec/cordova`.
Looking into the actual spec files, it seems to test functionality in these
files:
- /lib/cordova/post/addtitle
- /lib/cordova/post/prettify
- /lib/cordova/post/tableofcontents
- /lib/cordova/post/updateindex
- /lib/cordova/post/updatekeywordindex
- /lib/cordova/pre/yamlfrontmatter
Is the code being tested here actually still relevant for the current state of
the docs?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13945) `npm test` still relevant?
[
https://issues.apache.org/jira/browse/CB-13945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383625#comment-16383625
]
Jan Piotrowski (Sujan) commented on CB-13945:
-
[~dblotsky], do you know any about that?
> `npm test` still relevant?
> --
>
> Key: CB-13945
> URL: https://issues.apache.org/jira/browse/CB-13945
> Project: Apache Cordova
> Issue Type: Task
> Components: cordova-docs
>Reporter: Jan Piotrowski (Sujan)
>Priority: Major
>
> There are some tests in cordova-docs which can be run with `npm test`,
> described here:
> https://github.com/apache/cordova-docs/blob/master/doc/testing-the-website.md
> {code}
> C:\Projects\Cordova\cordova-docs (janpio-random_docs_stuff -> origin)
> (cordova-website@0.0.1)
> λ npm test
> > cordova-website@0.0.1 test C:\Projects\Cordova\cordova-docs
> > npm run eslint && npm run mocha
> > cordova-website@0.0.1 eslint C:\Projects\Cordova\cordova-docs
> > eslint tools/lib tools/spec
> > cordova-website@0.0.1 mocha C:\Projects\Cordova\cordova-docs
> > mocha --recursive tools/spec
> (node:11372) [DEP0006] DeprecationWarning: child_process: options.customFds
> option is deprecated. Use options.stdio instead.
> AddTitle
> √ should set the title
> √ should skip files with no source title
> √ should skip files with no target title
> Prettify
> √ should find some code blocks
> √ should add the prettyprint class to each code block
> TableOfContents
> √ should find the table of content values
> √ should find all elements
> √ should find all elements
> √ should ignore whitespace in the target name
> √ should create a HTML select element
> √ should skip files with no source title
> √ should skip files with no target title
> UpdateIndex
> √ should skip all files but index.md.html
> √ should rename the title
> √ should rename the file
> UpdateKeywordIndex
> √ should skip all files but _index.html
> √ should rename the title
> √ should rename the h1 (66ms)
> √ should remove the
> √ should update references from index.md.html to index.html
> YamlFrontMatter
> √ should skip files with no YAML Front Matter
> √ should parse files with YAML Front Matter
> FileHelpers
> - should have a default input directory that exists
> 22 passing (901ms)
> 1 pending
> {code}
> If you follow the trail, this seems to run the tests in `tools/spec/cordova`.
> Looking into the actual spec files, it seems to test functionality in these
> files:
> - /lib/cordova/post/addtitle
> - /lib/cordova/post/prettify
> - /lib/cordova/post/tableofcontents
> - /lib/cordova/post/updateindex
> - /lib/cordova/post/updatekeywordindex
> - /lib/cordova/pre/yamlfrontmatter
> Is the code being tested here actually still relevant for the current state
> of the docs?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13943) ERR_FILE_NOT_FOUND
[ https://issues.apache.org/jira/browse/CB-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Mudrick updated CB-13943: Priority: Minor (was: Major) > ERR_FILE_NOT_FOUND > -- > > Key: CB-13943 > URL: https://issues.apache.org/jira/browse/CB-13943 > Project: Apache Cordova > Issue Type: Bug > Environment: Android — any > Cordova — 6.5.0 >Reporter: Arthur Mudrick >Priority: Minor > Attachments: > Screenshot_2018-02-28-15-18-50-964_ru.balumates.balu.png, > Screenshot_2018-02-28-15-55-56-348_ru.balumates.balu.png > > > I use Angular with Cordova. Angular uses URL routing, e.g. `/login` for the > Login page, '/settings' for the Settings page, etc. > When Android application updates (when new application version is installed) > Cordova is like «reloads» itself or something, but the path in the address > bar was `/login` or `/users` or `/settings` etc., so, Cordova thinks it is a > folder. > Cordova throws an error — see screenshot #1 — there is a path `/www/users` > but the `/users` is just Angular's routing, not a folder to search for :) > I also tried to make Angular work with hashbang url strategy, e.g. `/#/login` > rather than `/login` — it throws another error, see screenshot #2. > So, basically Cordova behaves like a server without the `mod_rewrite` option > — it tries to find folders inside the `/www` folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13943) ERR_FILE_NOT_FOUND
[ https://issues.apache.org/jira/browse/CB-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Mudrick updated CB-13943: Environment: Android — any Cordova — 6.5.0 was: Android — any Cordova — 6.5.0 > ERR_FILE_NOT_FOUND > -- > > Key: CB-13943 > URL: https://issues.apache.org/jira/browse/CB-13943 > Project: Apache Cordova > Issue Type: Bug > Environment: Android — any > Cordova — 6.5.0 >Reporter: Arthur Mudrick >Priority: Major > Attachments: > Screenshot_2018-02-28-15-18-50-964_ru.balumates.balu.png, > Screenshot_2018-02-28-15-55-56-348_ru.balumates.balu.png > > > I use Angular with Cordova. Angular uses URL routing, e.g. `/login` for the > Login page, '/settings' for the Settings page, etc. > When Android application updates (when new application version is installed) > Cordova is like «reloads» itself or something, but the path in the address > bar was `/login` or `/users` or `/settings` etc., so, Cordova thinks it is a > folder. > Cordova throws an error — see screenshot #1 — there is a path `/www/users` > but the `/users` is just Angular's routing, not a folder to search for :) > I also tried to make Angular work with hashbang url strategy, e.g. `/#/login` > rather than `/login` — it throws another error, see screenshot #2. > So, basically Cordova behaves like a server without the `mod_rewrite` option > — it tries to find folders inside the `/www` folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13943) ERR_FILE_NOT_FOUND
[ https://issues.apache.org/jira/browse/CB-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Mudrick updated CB-13943: Priority: Major (was: Minor) > ERR_FILE_NOT_FOUND > -- > > Key: CB-13943 > URL: https://issues.apache.org/jira/browse/CB-13943 > Project: Apache Cordova > Issue Type: Bug > Environment: Android — any > Cordova — 6.5.0 >Reporter: Arthur Mudrick >Priority: Major > Attachments: > Screenshot_2018-02-28-15-18-50-964_ru.balumates.balu.png, > Screenshot_2018-02-28-15-55-56-348_ru.balumates.balu.png > > > I use Angular with Cordova. Angular uses URL routing, e.g. `/login` for the > Login page, '/settings' for the Settings page, etc. > When Android application updates (when new application version is installed) > Cordova is like «reloads» itself or something, but the path in the address > bar was `/login` or `/users` or `/settings` etc., so, Cordova thinks it is a > folder. > Cordova throws an error — see screenshot #1 — there is a path `/www/users` > but the `/users` is just Angular's routing, not a folder to search for :) > I also tried to make Angular work with hashbang url strategy, e.g. `/#/login` > rather than `/login` — it throws another error, see screenshot #2. > So, basically Cordova behaves like a server without the `mod_rewrite` option > — it tries to find folders inside the `/www` folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13943) ERR_FILE_NOT_FOUND
Arthur Mudrick created CB-13943: --- Summary: ERR_FILE_NOT_FOUND Key: CB-13943 URL: https://issues.apache.org/jira/browse/CB-13943 Project: Apache Cordova Issue Type: Bug Environment: Android — any Cordova — 6.5.0 Reporter: Arthur Mudrick Attachments: Screenshot_2018-02-28-15-18-50-964_ru.balumates.balu.png, Screenshot_2018-02-28-15-55-56-348_ru.balumates.balu.png I use Angular with Cordova. Angular uses URL routing, e.g. `/login` for the Login page, '/settings' for the Settings page, etc. When Android application updates (when new application version is installed) Cordova is like «reloads» itself or something, but the path in the address bar was `/login` or `/users` or `/settings` etc., so, Cordova thinks it is a folder. Cordova throws an error — see screenshot #1 — there is a path `/www/users` but the `/users` is just Angular's routing, not a folder to search for :) I also tried to make Angular work with hashbang url strategy, e.g. `/#/login` rather than `/login` — it throws another error, see screenshot #2. So, basically Cordova behaves like a server without the `mod_rewrite` option — it tries to find folders inside the `/www` folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
