-
Notifications
You must be signed in to change notification settings - Fork 15
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
Not working if the property name has camel casing in it. #18
Comments
This should work. The I'm not saying that there isn't a problem. There likely is and, even more likely, I'm misunderstanding your description :) But... I'll need a test case that demonstrates the problem. Would it be possible to modify the Karma tests in this repos to demonstrate the bug and submit a pull request? The PR doesn't have to include a fix, but a failing test would be fantastic. |
I have updated the paramter out to outValue... I have attached the codes below have a look x-double.html` ` index.html
check this.. this is failing. here doubled is not getting updated |
@eee-c : did you get a chance to look into the snippet i have provided. |
Much thanks for the snippet. I'm crazy swamped these days (who isn't I really appreciate the snippet -- it's a huge help! I think I see the On Sat, Sep 10, 2016 at 1:15 AM, Debananda Mohanty <notifications@github.com
|
The directive is not working for polymer property name with came casing. probably need to rewrite the regex again var match = $attr[prop].match(/{{\s([.\w]+)\s_}}/);
The text was updated successfully, but these errors were encountered: