feat: enhance FormWizard with navigation state management - #28
Conversation
- Added `isNavigating` state to track validation during step transitions. - Updated `handleNext` function to manage navigation state and prevent concurrent submissions. - Modified `renderActions` to include `isNavigating` for better UI feedback. - Adjusted button states to reflect navigation status, improving user experience.
|
|
🎉 This PR is included in version 1.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6f0d07f85a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@hookform/resolvers": "^5.4.0", | ||
| "@mui/material": "^9.2.0", |
There was a problem hiding this comment.
If anyone uses the tracked package-lock.json (for example an npm-based local setup or CI job), these package.json bumps are now out of sync with that lockfile: its root devDependencies still list old ranges such as @hookform/resolvers ^5.2.2 and @mui/material ^9.0.1. The npm ci docs specify that mismatched package-lock dependencies make the install exit instead of updating the lockfile, so please update package-lock.json alongside bun.lock or remove it if Bun is the only supported manager.
Useful? React with 👍 / 👎.
1 participant
isNavigatingstate to track validation during step transitions.handleNextfunction to manage navigation state and prevent concurrent submissions.renderActionsto includeisNavigatingfor better UI feedback.