GoogleWebComponents
Make demo and tests work on GitHub pages
I was going to try releasing a new version of the element, but was unable to verify that the demo works when I tried it locally. @marcacohen do you think you might have a chance to look at this?
I tested it yesterday. It works but require you to supply credentials and a GCP project ID.
I'm thinking about a demo and tests where the actual API calls to GCP are stubbed using a Service Worker. Need to prototype a bit. I'm going to use this issue as the progress tracker.
I'm still on leave through first week of Jan. I'll take a look at this when I get back on 5 Jan, though it sounds like Alex already has a plan. I'll synch with him on early Jan.
On Wed, Dec 17, 2014 at 1:51 PM, alex [email protected] wrote:
I tested it yesterday. It works but require you to supply credentials and a GCP project ID.
I'm thinking about a demo and tests where I the actual API calls to GCP are stubbed using a Service Worker. Need to prototype a bit. I'm going to use this issue as the progress tracker.
— Reply to this email directly or view it on GitHub https://github.com/GoogleWebComponents/google-cloud/issues/10#issuecomment-67324299 .
Marc Cohen [email protected] [email protected] http://about.me/marc1
I've ported beacon-send to Polymer 1.0. @ebidel, @marcacohen and me think we might be able to use it as a self-cleanup mechanism in some end2end tests.
As for the demo, I'm thinking to create a special one which would include authentication, so that:
- any resource creation will be billed to the authenticated user trying the demo
- it'll work in github pages