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

Update authentication example accessing state.errors #70028

Merged
merged 3 commits into from
Sep 16, 2024

Conversation

Francoscopic
Copy link
Contributor

  1. useFormState can't be found in the current react version, for some reason. Picking it from react-dom works just fine.
  2. Reading state.errors.name from the state object before it becomes defined returns a TypeError. Checking if it's defined first before calling its children works just fine.

1. "useFormState" can't be found in the current react version, for some reason. Picking it from "react-dom" works just fine.
2. Reading "state.errors.name" from the "state" object before it becomes defined returns a TypeError. Checking if it's defined first before calling its children works just fine.
@ijjk ijjk added the Documentation Related to Next.js' official documentation. label Sep 12, 2024
@ijjk
Copy link
Member

ijjk commented Sep 12, 2024

Allow CI Workflow Run

  • approve CI run for commit: b76b41f

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@ijjk ijjk changed the title Update index.mdx Update authentication example accessing state.errors Sep 16, 2024
@ijjk ijjk enabled auto-merge (squash) September 16, 2024 19:36
@ijjk ijjk merged commit e005cb5 into vercel:canary Sep 16, 2024
39 checks passed
@Francoscopic Francoscopic deleted the patch-2 branch September 16, 2024 21:34
ijjk pushed a commit that referenced this pull request Sep 17, 2024
## Summary
The error message should correspond to its value.
In addition, add `?` to the state of password like the others.

### Improving Documentation

- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

x-ref: #70028 

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
@github-actions github-actions bot added the locked label Oct 2, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation Related to Next.js' official documentation. locked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants