Releases: code-corps/ember-stripe-elements
Releases · code-corps/ember-stripe-elements
v0.4.0
Release 0.3.0
Upgrade Instructions
This change fixes a conflict where we had both an error
event and an error
on the Stripe Element component.
If you previously accessed the error
, e.g. by yielding to a block with your component, you should now prefer accessing stripeError
.
The error
event still fires as before.
Changelog
- #23 [BUGFIX] rearrange error setter close #22 @snewcomer
- #24 Upgrade to 2.17 @snewcomer
Release 0.2.2
- #21 [BUGFIX]
options
should default to an empty object
Release 0.2.1
- Fix issue where iframe could be undefined in integration tests (d488560)
Release 0.2.0
- Add lazy loading, mock Stripe, and improve test coverage (3b524fc)
- Add code coverage, only do coverage on ember releases, strip down integration tests, update .gitignore, update Ember to 2.14.2, run ember-modules-codemod (a69b630)
- Add stripe element and event to actions, schedule running Elements setup after insert to avoid rerender loop, add yarn.lock, include Stripe Element and event in actions, add complete action and send error, add eslint, fix eslint errors and remove phantomjs, update travis.yml, update ember-try, add testem args for chrome (5e9478b)
- Add paymentRequest to Stripe shim (#16) (f715078)
- ability to share elements when using stripe-card-* components (b559ff1)
- Add createSource, retrieveSource to stripev3 service (1875021)
This ain't no intro, this the entree
Changelog
This is the very first release, but it packs a pretty big punch.
- Release the components.
- Release the service.
- Write high-level documentation.
- Provide some examples in the dummy app.
What we need to do to get to 0.1.0-rc.1
+:
- Write tests! We don't need to over-test Stripe itself, but we should at least test that the portions of the API we use and expose are actually working as intended.
- Write some inline documentation.
- Test thoroughly in production.