You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There were two ideas behind introducing the apps:// pseudo-protocol to indicate links to the qooxdoo apps:
it made it possible to have local versions of the qooxdoo apps that could be linked to in the documentation. Docsify would dynamically reference the online or offline version dependent on whether it was run with qx serve or from the qooxdoo domain. However, we no longer ship the offline apps with the NPM release-
it would speed up linting as the links were considered to be safe. However, the links can be faulty if the apps change something in their approach to routing (which would be bad, because non-BC) or if there is something broken. The question is if the increase in speed is more valuable than alerting us to broken links.
I suggest we replace apps:// with real https:// links. This would also make them work when viewing the docs on GitHub. It would still be possible to implement some kind of dynamic redirection if we need it, based on those links.
The text was updated successfully, but these errors were encountered:
There were two ideas behind introducing the
apps://
pseudo-protocol to indicate links to the qooxdoo apps:qx serve
or from the qooxdoo domain. However, we no longer ship the offline apps with the NPM release-I suggest we replace
apps://
with realhttps://
links. This would also make them work when viewing the docs on GitHub. It would still be possible to implement some kind of dynamic redirection if we need it, based on those links.The text was updated successfully, but these errors were encountered: