Selector for form[formName].registeredFields
See original GitHub issueI have a use case where I’d like to be able to get a list of all the fields that have currently been registered on a form.
Basically I’m trying to do a kind of fancy wizard flow that necessitates having a list of all the field names, and I’d like to avoid typing them out on both the <Field>
s and in the container where the business logic is happening (keeping them in sync would be problematic as the form grows)
I don’t see a selector for form[formName].registeredFields
– is that intentional? If I make my own, is the field name likely to change?
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Selectors - Redux Form
redux-form provides a set of useful Redux state selectors that may be used in any part of your application to query the state...
Read more >reactjs - How to access pristine prop of reduxForm from inside ...
registeredFields.title : Question: Is there a way to get pristine property of my form inside another component or inside redux state?
Read more >How to use the redux-form.getFormValues function in ... - Snyk
To help you get started, we've selected a few redux-form.getFormValues examples, based on popular ways it is used in public projects.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No, you’re right @rizedr. There are no props for this either.
Thinking about this a little better… I recently developed a custom forms feature. The list of fields include whether the field is required, whether it requires emails/dates/etc. So I base my rules on these instead of something else. I highly recommend you guys to do something like this. It’s probably a bad idea to create dynamic rules based on fixed fields.
This is because one doesn’t exist.
I marked it as an enhancement, but please follow the template the next time you open an issue here. It was made for a reason.