Orion/API Changelog

This page lists breaking changes that may impact consumers of Orion API. This is maintained on a best-effort basis, and should not be taken as an exhaustive list.

Orion 9.0

Editor

• bug 461222: The HTML and CSS content assist providers no longer ship compiled into built-editor.js and built-editor.min.js. The caller is now responsible for loading their desired content assist provider(s) and registering them with the editor. This was done to reduce download size.

Build

• bug 461530: System properties that disable portions of the Orion Maven build, such as orion.client.build.skip and skipJsdoc, must now be assigned a value true or false. Prior to Orion 9.0, the values did not matter, and any system property was effectively "true". This was done to reduce confusion and make the build easier to script from Hudson/Jenkins.
  For example:
  • -Dorion.client.build.skip=true will skip all client-side minification.
  • -DskipOrionUI=true will skip minification of the Orion pages and plugins.
  • -DskipJsdoc will not skip JSDoc.

Orion 8.0

Internationalization (i18n)

• The orion.i18n.message service has been removed.
• Translation is no longer provided through the plugin registry. Message bundles cannot be installed at runtime by the user.
• Any nls properties on services registered with a PluginProvider are ignored. Other NLS-related properties, such as nameKey, descriptionKey, etc, are also ignored.
• Plugins are expected to perform translation themselves, using any appropriate strategy (such as RequireJS i18n plugin, for example). Any user-facing labels or strings returned by services (such as validation error messages, or command labels) are now expected to be translated into the user's locale if possible. The Orion UI framework will no longer load message bundles nor look up strings on behalf of a plugin.