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

[Snyk] Upgrade @formspree/react from 2.5.0 to 2.5.1 #334

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

Conversation

devarshishimpi
Copy link
Member

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade @formspree/react from 2.5.0 to 2.5.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on 9 months ago.

Release notes
Package name: @formspree/react
  • 2.5.1 - 2023-08-23

    Patch Changes

  • 2.5.0 - 2023-08-03

    Minor Changes

    • 4c40e1b: # Fix types in @ formspree/core

      @ formspree/core

      • fix SubmissionData has a type of any causing everything after it to opt-out typechecking
      • remove a no-op teardown method on Client and Session
      • remove utils.now and use Date.now instead
      • remove unused functions from utils module: append, toCamel, camelizeTopKeys
      • add tests for utils.appendExtraData and convert the test file to typescript
      • add tests for session.data()
      • no longer export Session type

      @ formspree/react

      • update types as a result of SubmissionData is no longer any
      • fix createPaymentMethod does not properly map payload when the submission data is a type of FormData
      • fix the Client is not updated when project changes
    • 49730d9: ## Improve error handling

      • @ formspree/core submitForm function now will never rejects but always produces a type of SubmissionResult, different types of the result can be refined/narrowed down using the field kind.
      • Provide SubmissionErrorResult which can be used to get an array of form errors and/or field errors (by field name)
      • Response is no longer made available on the submission result
      • Update @ formspree/react for the changes introduced to @ formspree/core
    • d025831: @ formspree/core

      • rename client config stripePromise to stripe since it expects the resolved Stripe client not a promise

      @ formspree/react

      • add a new hook: useSubmit which is suitable with code that uses other ways to manage submission state (e.g. with a library like react-hook-form)
      • update useForm to use useSubmit under the hood
      • fix: FormspreeContext updates the client when props.project change

    Patch Changes

from @formspree/react GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @formspree/react from 2.5.0 to 2.5.1.

See this package in npm:
@formspree/react

See this project in Snyk:
https://app.snyk.io/org/devarshishimpi/project/69511316-b884-4a6d-b81f-548b43321ca0?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @devarshishimpi, Thanks for contributing and Congrats on opening PR 🎉.

We will try to review as soon as possible and a maintainer will get back to you soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants