This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
feat(hook): add useOnFieldChange #575
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
philibea
requested review from
chambo-e,
matthprost,
DorianMaliszewski and
QuiiBz
philibea
force-pushed
the
hook-onfieldchange
branch
5 times, most recently
from
41e7592 to
c2e36c7
Compare
QuiiBz
approved these changes
Dec 22, 2022
philibea
force-pushed
the
hook-onfieldchange
branch
from
ff73138 to
3a0c577
Compare
matthprost
approved these changes
Dec 22, 2022
scaleway-bot
pushed a commit
that referenced
this pull request
Dec 22, 2022
## [1.36.0](v1.35.8...v1.36.0) (2022-12-22) ### ⚙️ Features * **hook:** add useOnFieldChange ([#575](#575)) ([e5826fb](e5826fb))
|
🎉 This PR is included in version 1.36.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Type
Summarise concisely:
What is expected?
Add a clear hook useOnFieldChange to avoid using useEffect on our Form.