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
Add optional <apollo-query> and <apollo-mutation> elements #11
Comments
Although I won't like to use custom elements for my queries I think this could be useful for some. |
Could take it as a property. Might mean needing to reevaluate the order of
operations when setting the client e.g. first setting query, afterwards
setting client.
On Tue, Jul 24, 2018, 4:55 PM Alessio Occhipinti ***@***.***> wrote:
Although I won't like to use custom elements for my queries I think this
could be useful for some.
I'm not sure, but how will these elements share the apollo-client? I'll
should pass it down?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZgNIs3XJrkEBOTSKgnB3xet45cInH7ks5uJydfgaJpZM4VcaKA>
.
--
Benny Powers
Licensed Israel Tour Guide
In Israel 054-482-5726
In Canada 705-300-0072
In the USA 601-255-3532
bennypowers.com
|
I'm interested in They will help users migrate from polymer-apollo-client. |
Just found that on https://webcomponents.org/element/lit-apollo page It looks strange, because I haven't found
@bennypowers How is that even possible? 🤔 |
Probably some mismatched JSDoc comments |
Closed by d056b63 If problem persists after next release, feel free to reopen. |
I'm thinking we can distribute optional
elements/apollo-query.js
andelements/apollo-mutation.js
that would basically follow the pattern set out in the README@LasaleFamine @FluorescentHallucinogen What do you think about that? I think we can start experimenting with the design for
<apollo-mutation>
set out in #2 (comment) and see where it takes us.The text was updated successfully, but these errors were encountered: