Skip to content
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

Bump react-stripe-elements from 2.0.3 to 6.1.2 #145

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

Bumps react-stripe-elements from 2.0.3 to 6.1.2.

Release notes

Sourced from react-stripe-elements's releases.

v6.1.2

Bug Fixes

  • Fix a bug where the elements prop is not injected by injectStripe when using async Stripe and mounting only a CardCvcElement or CardExpiry Element. (#519 )

v6.1.1

Changes

  • Register package version with Stripe instance (#512)

v6.1.0

New Features

Added the auBankAccount and fpxBank elements. These elements will not have automatic Element detection/insertion. To use them you will need to use elements.getElement and pass them directly to other Stripe.js methods (e.g. stripe.confirmFpxPayment):

const FpxForm = injectStripe(({stripe, elements}) => {
  const handleSubmit = async (event) => {
    event.preventDefault();
    const {error} = await stripe.confirmFpxPayment('{{CLIENT_SECRET}}', {
      payment_method: {
        fpx: elements.getElement('fpxBank'),
      },
    });
  }
return (
<form onSubmit={handleSubmit}>
<FpxBankElement accountHolderType="individual" />
<button>Pay</button>
</form>
);
});

v6.0.1

Version bump that fixes some typos, no changes.

v6.0.0

New Features

  • injectStripe now injects a reference to the Elements instance created by <Elements> as the prop elements.

The primary reason you would want an Elements instance is to use elements.getElement(), which provides an easy way to get a reference to an Element. You will need to get a reference to an Element to use confirmCardPayment, confirmCardSetup(), or createPaymentMethod().

Note that the old API for createPaymentMethod will continue to work and provide automatic element injection, but we are updating documentation and examples to use the new argument shape:

</tr></table> ... (truncated)
Changelog

Sourced from react-stripe-elements's changelog.

Changelog

react-stripe-elements adheres to Semantic Versioning.

v6.1.1 - 2020-04-01

Changes

  • Register package version with Stripe instance (#512)

v6.1.0 - 2020-02-14

New Features

Added the auBankAccount and fpxBank elements. These elements will not have automatic Element detection/insertion. To use them you will need to use elements.getElement and pass them directly to other Stripe.js methods (e.g. stripe.confirmFpxPayment):

const FpxForm = injectStripe(({stripe, elements}) => {
  const handleSubmit = async (event) => {
    event.preventDefault();
    const {error} = await stripe.confirmFpxPayment('{{CLIENT_SECRET}}', {
      payment_method: {
        fpx: elements.getElement('fpxBank'),
      },
    });
  };
return (
<form onSubmit={handleSubmit}>
<FpxBankElement accountHolderType="individual" />
<button>Pay</button>
</form>
);
});

v6.0.1 - 2019-11-13

Version bump that fixes some typos, no changes.

v6.0.0 - 2019-11-13

New Features

  • injectStripe now injects a reference to the Elements instance created by <Elements> as the prop elements.
... (truncated)
Commits
Maintainer changes

This version was pushed to npm by dweedon-stripe, a new releaser for react-stripe-elements since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants