New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
data binding doesn't work if binding contains reserved word in Dart #19069
Comments
Removed Area-Polymer label. |
Removed Library-PolymerExpressions label. |
I don't think this is a big deal. JS interop works via String names right now, and when we have Dart interfaces for them they won't be able to use reserved words as property names, so any translation will have to happen there. If we want to add special support for dart:js.JsObject in PolymerExpressions we can still only create new Symbol objects after we determine the receiver is just a plain Dart object. |
ok - this still needs to be fixed in the codegen. Script_compactor shouldn't generate getters for these keywords. Added this to the 1.6 milestone. |
Removed this from the 1.6 milestone. |
Removed Polymer-P-1 label. |
Added PolymerMilestone-Next label. |
Removed Polymer-Milestone-Next label. |
@jakemac53 ... this might get fixed in new polymer? |
We still are using smoke to read properties (at least for now), so I think this is still an issue. |
This issue has been moved to dart-archive/polymer-dart#398. |
we'll need to figure out something so we can bind to JS props with those names...
perhaps a name mangling scheme or something else. it is primarily a concern because of interop -- otherwise would be fine to not support them.
https://codereview.chromium.org/303003003/diff/20001/pkg/polymer/test/build/script_compactor_test.dart?column_width=80
The text was updated successfully, but these errors were encountered: