Data binding doesn't parse Japanese unicode characters

[ajiang286]

Version 1.6.1:

value="{{data.商品名}}"
evaluates to the string "{{data.商品名}}" instead of dereferencing data.商品名

[ajiang286]

Seems to happen for any non-English/numeric unicode

[kevinpschaaf]

The binding parser only considers valid javascript identifiers for path bindings.

However, as long as you don't need 2-way binding, you can use [[get('...')]] to retrieve paths using arbitrary characters by leveraging computed bindings and the get method that exists on the Polymer base class: http://jsbin.com/qucada/edit?html,output

If you need 2-way bindings to paths, you'll need to restrict the data model to valid JS identifiers.

Will one of those solutions work for you?

[ajiang286]

I was able to come up with a solution based on your response. Thanks!

[TimvdLippe]

Closing per above comment.

[arthurevans]

FYI, at least as of ES2015, I believe that the MDN article is wrong (or oversimplified) and that this is a valid JS identifier. The standard basically says that it should use one of the valid Unicode identifier characters:

https://www.ecma-international.org/ecma-262/6.0/index.html#sec-names-and-keywords

The related Unicode standard is here:

http://unicode.org/reports/tr31/

And if you look at the characters here, it appears that they're valid for identifiers. For example:

http://www.fileformat.info/info/unicode/char/5546/index.htm

And V8 don't seem to mind them at all:

[TimvdLippe]

Oh oops. After I closed this issue, I realized exactly the same, but did not reopen this issue. Thanks for doing so @arthurevans ! Note that I published #4768 that solves this particular issue as well 🎉