-
Notifications
You must be signed in to change notification settings - Fork 179
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
feat(core): remove account status provider with toast messages #1749
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
@@ -35,5 +35,5 @@ test('Account is not created if email is already in use', async ({ page, account | |||
|
|||
await page.getByRole('button', { name: 'Create account' }).click(); | |||
|
|||
await expect(page.getByText('The email address is already in use.')).toBeVisible(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just had to fix an issue in the wordpress issue, but this is a security concern allowing bad actors find out if email addresses are valid. Changed it over to a more generic error.
cf4c191
to
005d7aa
Compare
🦋 Changeset detectedLatest commit: 005d7aa The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
⚡️🏠 Lighthouse reportLighthouse ran against https://catalyst-latest-6gsjqvwr8-bigcommerce-platform.vercel.app 🖥️ DesktopWe ran Lighthouse against the changes on a desktop and produced this report. Here's the summary:
📱 MobileWe ran Lighthouse against the changes on a mobile and produced this report. Here's the summary:
|
What/Why?
Remove the rest of the account status provider usages and move over to using toasts.
I also had to adjust a few things for all the pages to work correctly:
login
route was statically generated, which prevented an auth check on the page. Needed to remove that static generation.Testing
Updated and ran the test suite to verify all functionality worked the same.