[email protected]; soft fail on broken translations (#244)

gadicc · Sep 5, 2016 · 7b1c8af · 7b1c8af
1 parent 9b350a1
commit 7b1c8af
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -35,7 +35,7 @@ Current versions of each package (requires manual, explicit updates until
 the stable release; consider backing up your database before upgrading):
 
 ```
-meteor add msgfmt:[email protected].21         # 2016-04-13
+meteor add msgfmt:[email protected].23         # 2016-09-05
 
 # released packages
 meteor add msgfmt:extract                       # 2016-04-01 (v2.0.0)

diff --git a/packages/core/History.md b/packages/core/History.md
@@ -1,5 +1,13 @@
 ## vNEXT
 
+## v2.0.0-preview.23 (2016-09-05)
+
+### Changed
+
+* "Broken" translations (that can't be compiled) are no longer displayed as
+  `[Object object]`; instead the native string will be shown and an error
+  logged on the console.  Thanks, @sbalmer! (#244)
+
 ## v2.0.0-preview.22 (2016-05-31)
 
 ### Fixed

diff --git a/packages/core/package.js b/packages/core/package.js
@@ -1,6 +1,6 @@
 Package.describe({
   name:    "msgfmt:core",
-  version: "2.0.0-preview.22",
+  version: "2.0.0-preview.23",
   summary: "MessageFormat i18n support, the Meteor way",
   git:     "https://github.com/gadicc/meteor-messageformat.git",
   documentation: 'README.md'