search

webcomponents / webcomponents.org

Home of the web components community
https://www.webcomponents.org
Apache License 2.0
359 stars 95 forks source link

Polymer version #980

Open chasb154 opened 7 years ago

chasb154 commented 7 years ago

Origin page

I'm looking for elements but I've switched over to Polymer 2.0. I need to be able to see Polymer version on the list. I find myself opening every element on my search results and closing the ones that are Polymer 1.0.

It would be great to see Polymer version on returned search results.

madeleineostoja commented 7 years ago

Sets a dangerous tie-in precedent with Polymer - what about elements not using Polymer? Or a WC framework at all? Think this would be better addressed with tags (making them more prominent? Documenting the pattern for component authors to follow?) or a general dependency:name#version or similar search operator

chasb154 commented 7 years ago

Good Point. As the web components become more broadly used there will be more varied dependency requirements. Right now I'm only concerned about dependencies on Polymer but that's my choice due to the ecosystem and support for it.

Your idea for tags is better and, I think, going to be needed soon if web components continue to grow.

jaakidup commented 7 years ago

What is the latest idea regarding this issue? It is becoming a real thing to only find compatible components

stramel commented 7 years ago

Maybe having a libraries filter?

These could probably be populated based on what libraries and versions the components in the catalog depend on?

Link2Twenty commented 6 years ago

Would filter by dependencies be best?

chasb154 commented 6 years ago

Hit close by mistake.