no-issue
This is to avoid any weirdness around the two requests for signup to a
paid site. First we have the signup request, and then we have the create
subscription request. After the first signup request a "signedin" event
is fired, fetching a token, but one without any plans.
no-issue
This is needed so that we can request a brand new token from layer1, in
the instance of knowing user data has changed, we can have a token whihc
reflects it.
* Pass container from layer2 for iframes to be attached
* Updated layer2 to resolve with success for auth page methods
* Updated theme dropin to reload when auth method succeeds
* Ignored build
* Deleted build dir
* Updated layer1 to interface with simplified gateway
* Updated layer1 to only handle gateway
* Updated layer2 to handle gateway & auth, but no DOM
* Updated theme dropin to handle DOM
* Updated layer2;
* Added password-reset flow to the member dropin script
* Reload page after password reset
* Created initial layer0 sdk
* Updated layer1 to use layer0
* Updated layer2 to accept and pass blogUrl to layer1
* Updated theme-dropin to pass blogUrl to layer2
* Updated yarn.lock
* Added WIP drop-in script for prototype
* Cleaned up theme dropping script module
- Updated layer2 to work with reload as an option, as well as sign-in cta on the page
* Handle cat failure
* Updated SDK data attires
* Used commonjs exports
* Used browserify for the build
