Skip to content

Conversation

@atapas
Copy link
Member

@atapas atapas commented Apr 21, 2022

Description

Upgrade to React 18

Fixes # (issue) #87

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@atapas atapas self-assigned this Apr 21, 2022
@vercel
Copy link

vercel bot commented Apr 21, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/atapas/react-play/87RXr3LEWxs5GDmh5Aq8i1s8Qmjw
✅ Preview: https://react-play-git-upgrade-react-18-atapas.vercel.app

@atapas atapas merged commit 8e4393b into main Apr 21, 2022
@atapas atapas deleted the upgrade-react-18 branch April 21, 2022 12:48
@atapas atapas linked an issue Apr 21, 2022 that may be closed by this pull request
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.

✨ [Feature request]: Upgrade to Raect v18

2 participants