react-component / react-component/field-form
onFieldsChange/onValuesChange triggers with only single field/value even if multiple are changed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 286
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 1
Description
I am not sure if this is expected behavior, but if I have a form with say,
initialValues = {
fieldA: 'foo',
fieldB: 'bar
}
and I change foo to qwe
and bar to rty.
The second time it will trigger with only qwe -> rty even though foo is changed to qwe
I would expect it to contain 2 changed fields.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the described form with two changed fields and inspect the onFieldsChange/onValuesChange behavior. Trace the relevant callback implementation and verify that both changed fields are reported together when multiple values change; the issue provides no file or test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100