react-component / react-component/field-form
Semver and getFieldsValue(bool)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 286
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 1
Description
regarding big change to form.getFieldsValue() and form.getFieldValues(true).
semver not respected. antd-rc5 takes a npm dependency using ^ on this in a tagged release and so now we have unpredictable builds and big behaviourable changes with regards to forms.
What is 0.0.0-rc6 meant to represent logically?
#versioning #semver #breaking
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 reviewing the getFieldsValue() and getFieldValues(true) API history alongside the antd-rc5 dependency declaration and tagged release metadata. Compare the behavior change with the stated semver expectations; done means the versioning decision and the intended meaning of 0.0.0-rc6 are explicit and consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100