Remove configuration settings from the compiled JS to be more polymer-esque.

[paales]

Hi there!

Thanks for the work on the polymer module! Trying out your module at the moment :)

The idea with Polymer is that you can import an element and use that without any knowledge about the internals.

I think the API should be something like this:

<apollo-client name="clientname" config='{ "uri": "https://myendpoint" "connectToDevTools": true }'></apollo-client>

Then in your element do something like:

behaviors: [
    Apollo.behavior('graphcms')(...query)
]

This currently causes an issue with the lifecycle. Because the element apollo-client is intialized later dan the behaviors are parsed..

Maybe there should be an element that allows you to create a query like so:

<apollo-query query="bla" params="{bla}" result="[[queryResultData]]"></apollo-query>

[eskan]

hi paales,
Is it useful to declare a global singleton as an element ? but i agree that created a behavior at compile time is a bit tricky.
Once that done, using apollo client with kapton is very easy and readable, especially with mutation (.. and promise).
When i've started using Kapton i thought about but i don't need it finally. Most of the time an element use one query which is bind to "data". I like that ui is in template and data/logical are in behavior/js.