onDynamicListenTo does not exist
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start in the validators section of the form.Field API and compare the existing ListenTo options with onDynamic. Locate the onDynamic definitions and their surrounding JSDoc, then confirm the work is done when the linked-field option and equivalent behavior documentation are present.
Written by the indexing model from the issue text.
Description
Describe the bug
Not sure if this should be listed as a bug or feature request. I noticed there was the recent addition of the onDynamic validation options, which is awesome! However, the validators section of a form.Field does not provide an onDynamicListenTo option to link the fields and the current props are missing JSDoc comments which are present for the other options.
Your minimal, reproducible example
N/A
Steps to reproduce
- Add to the validators section of a
form.Fieldcomponent - Note there is no
onDynamicListenToprop, but there is anonDynamicoption - The other validator props have a
ListenTooption to link fields - The new
onDynamicoptions also do not have JSDoc comments describing behavior
Expected behavior
OnDynamic should have an onDynamicListenTo prop to allow for linking fields with the onDynamic validation. I also would expect the onDynamic props to have JSDoc comments like the other fields have.
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
- Version: 1.19.2
TanStack Form adapter
react-form
TanStack Form version
1.19.2
TypeScript version
v5.8.3
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 6.7k
- Forks
- 682
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 7
Contributor guide
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.
More from TanStack/form
-
Difficulty 2/5 1-2 days Newbie friendliness 72/100
-
area: runtime scope: devtools type: bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
area: runtime scope: core type: bug v1
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
FormApi: onSubmit/onServer error cleared on any non-matching validation cause, not just 'change' Openv1 v2: needs investigation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
v1 v2: needs investigation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100