Closed rwestlund closed 5 years ago
@bendavis78 Is this in road map? If so any estimated date please..
Sent a pull request to support Polymer 2.0.
In fact, there are still changes to be mande in paper-time-picker and paper-clock-selector. I'm having errors with property-accessors
related to query-selector and/or dom-if
Did you get any problem like this? In general the component works well, but you have to tap the hour/minute before selecting its value, might be related to this query-selector error.
@bendavis78 Can we expect it to support Polymer 2 any soon?
@amanshu-kataria I'll be putting out a PR to support hybrid when I get some free time, sorry for being so inactive on here, promised I'd do some stuff to help out a while back and got slammed with work!
I saw that. I've been migrating a lot of elements to hybrid at work and creating a few new ones as well so I've got the pattern down pretty solid, just need some free time to write some tests before I start the conversion to ensure I don't break anything
@admwx7 please let me know what all I can do to help you. I would love to. :)
I'm hoping to push the testing scaffold with a few basic tests and version bump this weekend, after that if you want to add some additional tests, that would be great!
On Fri, Sep 15, 2017, 11:29 AM Amanshu Kataria notifications@github.com wrote:
@admwx7 https://github.com/admwx7 please let me know what all I can do to help you. I would love to. :)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bendavis78/paper-time-picker/issues/53#issuecomment-329832275, or mute the thread https://github.com/notifications/unsubscribe-auth/ABpRr8QDK25HF-2hk-pGDxVsEYyLGNn2ks5siqXVgaJpZM4NKpcr .
^1.2.0 should pick up the release candidate tag I just added against these changes, anyone feel daring enough to give it a try? We'll be integrating things on our side in the near future and releasing an official 1.2.0 once we've gone through that but additional testing in other apps would be nice.
I've been using 1.2.0-rc2 in production for several months now with no problems. Let's make it official and move on to Polymer 3 support.
No one has complained, closing this out.
Any plans to make this a hybrid element compatible with Polymer 2.0?