Skip to content
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

Publish on https://webcomponents.org #21

Open
FluorescentHallucinogen opened this issue Feb 24, 2018 · 9 comments
Open

Publish on https://webcomponents.org #21

FluorescentHallucinogen opened this issue Feb 24, 2018 · 9 comments

Comments

@FluorescentHallucinogen
Copy link
Collaborator

IMO, polymer-apollo should be a Polymer web component (or set of Polymer web components), i.e. HTML files.

@FluorescentHallucinogen
Copy link
Collaborator Author

If I understand correctly, polymer-apollo is a mixin (what is called behavior in Polymer 1.x) that helps access apollo-client instance in other Polymer web components.

I mean that behaviors (for Polymer 1.x), or mixins (for Polymer 2.x and Polymer 3.x) can be declared in the web components (in HTML file for Polymer 1.x and Polymer 2.x and published to Bower or in JS file for Polymer 3.x and published to NPM). See e.g. https://webcomponents.org/search/behavior.

See also https://webcomponents.org/element/reach-digital/polymer-apollo-client. This is a collection of <graphql-client>, <graphql-mutation> and <graphql-query> Polymer web components. It is very easy and intuitive to use it, but I don't know how flexible this design for complex scenarios. BTW, polymer-apollo-client doesn't support subscriptions.

@aruntk What do you think?

@FluorescentHallucinogen
Copy link
Collaborator Author

@paales @rjspotter What about to join efforts and work together on one single project? 😉

@aruntk
Copy link
Owner

aruntk commented Feb 25, 2018

What about to join efforts and work together on one single project

@FluorescentHallucinogen Sure. :)

@FluorescentHallucinogen
Copy link
Collaborator Author

@aruntk What about my suggestions?

@rjspotter
Copy link

rjspotter commented Mar 8, 2018

@FluorescentHallucinogen I'm happy to help out however I can. FWIW I chose to use polymer-apollo-client because the component model was easier to wrap my head around and integrate into a basic starter-kit (I'm primarily a Backend Dev)

@aruntk
Copy link
Owner

aruntk commented Mar 8, 2018

@FluorescentHallucinogen I've sent you a collaborator invitation. I'm a bit busy now-a-days. It'd be great if you could contribute. :)

@FluorescentHallucinogen
Copy link
Collaborator Author

I've also found https://github.com/atoy40/kapton by @atoy40 and https://github.com/matteo-hertel/polymer-graphql by @matteo-hertel.

@paales
Copy link

paales commented Jun 4, 2018

@FluorescentHallucinogen
Copy link
Collaborator Author

FluorescentHallucinogen commented Jun 5, 2018

@paales lit-apollo is great project, but it does not provide web components per se, this is base classes which authors are meant to extend. See apollo-elements/apollo-elements#2 for more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants