Skip to content

v1.2.0

Compare
Choose a tag to compare
@dchambers dchambers released this 19 Nov 12:55
· 457 commits to master since this release

BladeRunnerJS v1.2.0

BladeRunnerJS v1.2.0 contains a number of minor changes and features. It's backwardly compatible with BladeRunnerJS v1.1.

Improvements to missing i18n translation handling

The handling of missing i18n translations has been changed to provide better feedback to developers and translators when there are missing translations, while still ensuring that the app does the best job it can with the translations it has available when running in production. The exact behaviour is described below.

In Production (via brjs build)

Tokens within HTML templates

The translator first attempts to find a replacement for the active locale, but falls back to using the default locale if one isn't available, causing a warning to be logged to the terminal. If there isn't even a fall-back translation available the build will fail with an error message.

Tokens accessed programmatically in JavaScript

The translator first attempts to find a replacement for the active locale, but falls back to using the default locale if one isn't available, causing a warning to be logged to the browser's console at run-time. If there isn't even a fall-back translation available, a translation of ??? token.name ??? will be used, and an error will be logged to the browser's console at run-time.

In Development (via brjs serve)

Tokens within HTML templates

The translator first attempts to find a replacement for the active locale, but falls back to displaying a translation of ??? token.name ??? if one isn't available, causing a warning to be logged to the browser's console. In the case where a translation isn't even available in the default locale then logging occurs at error level rather than warning level.

Tokens accessed programmatically in JavaScript

The translator first attempts to find a replacement for the active locale, but falls back to using the default locale if one isn't available, causing a warning to be logged to the browser's console. In the case where a translation isn't even available in the default locale then logging occurs at error level rather than warning level.

Added a --js-minifier setting to test command

The test command now has the option of specifying the minifier used when building the bundles/js/bundle.js test bundle; previously, combined was always used. The minifier can be specified by using the --js-minifier flag when running tests (e.g. brjs test myApp UTs --js-minifier closure-simple), where this flag accepts the same set of minifiers as supported by the <@js.bundle ...@/> tag that's used within index.html pages.

Note: The minifier flag only configures the minifier to use when a logical path of bundles/js/bundle.js is used. Fully specified paths will continue to use the defined minifier. For example, closure-whitespace would be used if the path was bundles/js/dev/closure-whitespace/bundle.js, regardless of the command line setting.


API Documentation

Travis Build Status for v1.2.0:   Build Status

Closed Issues

The following issues labelled bug, feature, enhancement, experience, breaking-change, java-api, js-api or CaplinSupport have been closed:

  • Make Observable.getAllObservers public #1575
  • CSS bundler does not resolve file paths specified in IE filters #1574
  • Add getter function for Properties #1570
  • index.html missing from non default aspect when app has a single locale #1568
  • Improve error when i18n token is missing #1564
  • Aspects with a hyphen in the name aren't accessible without a trailing / in the URL #1562
  • Bugfix jquery auto complete box blur in ie8 #1559
  • Treat linux64 as a seperate browser 'OS' #1543
  • Help command improvements #1541
  • Add destroy method for jQueryAutoCompleteControl to clean listeners #1529
  • throw an exception if an app is missing jars and a WAR is being built #1525
  • Provide a closure-medium obfuscation setting #1504
  • App deployed in tomcat root causes extra slash to appear in url #1487
  • Error thrown when building app with i18n token #1462
  • Create a Keybinding service #1428
  • New bundle path in tests #1371
  • [feature] App level alias override #1071

38 issues closed; 17 labelled bug, feature, enhancement, experience, breaking-change, java-api, js-api or CaplinSupport from 1 milestones:
https://github.com/BladeRunnerJS/brjs/issues?milestone=43&state=closed

Found an Issue?

Parts of this release note have been auto-generated. If you notice any problems with it tell us