Translations containing backslashes

• I am on the latest ember-intl version
• I have searched the issues of this repo and believe that this is not a duplicate

Environment

• Ember Version: 3.1.0
• Ember CLI Version: 3.1.0
• Ember Intl Version: 3.2.6
• Browser(s): Chrome latest
• Node Version: 8.9.4

Steps to Reproduce

1. Add a translation that contains backslashes e.g.,

email:
    formats:
      default: '^.+@.+\.\w+$'

The reason we return a regex in translations it to ensure consistency in UI and API validations i.e., both the UI and API use this regex.

1. Try to load the translation in your app with intl.t('email.formats.default')

View the peg$SyntaxError error in the console:

{
  "message": "Expected \"\\\\#\", \"\\\\\\\\\", \"\\\\u\", \"\\\\{\", \"\\\\}\", \"{\", [^{}\\\\\\0-\\x1F\\x7f \\t\\n\\r], end of input or whitespace but \"\\\\\" found.",
  "expected": [
    {
      "type": "literal",
      "value": "\\#",
      "description": "\"\\\\#\""
    },
    {
      "type": "literal",
      "value": "\\\\",
      "description": "\"\\\\\\\\\""
    },
    {
      "type": "literal",
      "value": "\\u",
      "description": "\"\\\\u\""
    },
    {
      "type": "literal",
      "value": "\\{",
      "description": "\"\\\\{\""
    },
    {
      "type": "literal",
      "value": "\\}",
      "description": "\"\\\\}\""
    },
    {
      "type": "literal",
      "value": "{",
      "description": "\"{\""
    },
    {
      "type": "class",
      "value": "[^{}\\\\\\0-\\x1F\\x7f \\t\\n\\r]",
      "description": "[^{}\\\\\\0-\\x1F\\x7f \\t\\n\\r]"
    },
    {
      "type": "end",
      "description": "end of input"
    },
    {
      "type": "other",
      "description": "whitespace"
    }
  ],
  "found": "\\",
  "location": {
    "start": {
      "offset": 6,
      "line": 1,
      "column": 7
    },
    "end": {
      "offset": 7,
      "line": 1,
      "column": 8
    }
  },
  "name": "SyntaxError"
}

[jasonmit]

The original parser messageformat-parser which intl-messageformat-parser was derived from has quote escaping and allows backslashes now. I’ve begun to port the logic over to the intl-messageformat-parser.

This will end up being a breaking change as it removes backslash as a special character for escaping in favor of the ICU spec quote escaping. I’ll version accordingly once this is ready for me to merge.

[jasonmit]

After updating the translation parser and compiler, this should now be resolved on master. Single quotes now properly escapes characters within the ICU syntax.

There are many breaking changes so will be releasing a 5.0.0-unstable shortly while I document all the breaking changes.