-
Notifications
You must be signed in to change notification settings - Fork 66
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
Polymer 3 support #121
Comments
Yeah, it is in the plans, but it might take a while. The other option i am
thinking is a complete re-write to be only Polymer 3 compatible and to only
provide the pop-up part. The input field part should be handled by the
user, but they are just my first thoughts on this. What do you think?
…On Sat, May 12, 2018, 23:59 Oliver Hamlet ***@***.***> wrote:
This may be a bit premature, but are there any plans for this element to
support Polymer 3, i.e. ship as an ES6 module published on the NPM registry?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#121>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAUumdEVyMHE6HXkAQXcYutrMFCDh-Vzks5txvjjgaJpZM4T8cdc>
.
|
I think that would be more flexible, but I don't have any strong opinion either way. The element works well for me as it is. 🤷♂️ |
Hi @jhuesos It would be nice to publish v3.0 with the same API and only after that adding new features. Developers already requiring v3.0. Thanks. |
Noted. I'm this week on holidays outside the country. I will do my best to
do this once I'm back. Of course, PR are always welcome :)
…On Tue, May 22, 2018, 03:10 Makhambet ***@***.***> wrote:
Hi @jhuesos <https://github.com/jhuesos> It would be nice to publish v3.0
with the same API and only after that adding new features. Developers
already requiring v3.0. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUumTsGZkryaSElEg3w0pHz-RGse8Zhks5t0wMpgaJpZM4T8cdc>
.
|
@jhuesos https://github.com/stat92/paper-autocomplete/tree/3.0-preview . Here analysis.json doesn't generated properly and components page doesn't have link to the demo. But component works OK. You can use it. |
I'm also interested in a Polymer 3 version (npm package). |
is this still in the works or stalled? Just asking as we migrate to Polymer 3 and rely on paper-autocomplete (which is fine as is). Eventually we'll do the migration ourselves. |
Someone made a Polymer 3 version, it works okay for me: |
This may be a bit premature, but are there any plans for this element to support Polymer 3, i.e. ship as an ES6 module published on the NPM registry?
The text was updated successfully, but these errors were encountered: