Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc] Fix FormDataConsumer usage example #8189

Merged
merged 4 commits into from
Sep 22, 2022
Merged

Conversation

WiXSL
Copy link
Contributor

@WiXSL WiXSL commented Sep 22, 2022

Fixes #8179

docs/Inputs.md Outdated Show resolved Hide resolved
docs/Inputs.md Outdated Show resolved Hide resolved
Co-authored-by: Francois Zaninotto <francois@marmelab.com>
@afilp
Copy link
Contributor

afilp commented Sep 23, 2022

I think that this may be an issue when hiding/showing filters too. At least this is what happened with a custom filter of mine when pressing the "clear" ("x") button. The query was still sending the filter value. If this is true, how can we "unregister" in filters form?

@fzaninotto
Copy link
Member

You'll have to write your own filter form.

https://marmelab.com/react-admin/FilteringTutorial.html#building-a-custom-filter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFR Ready For Review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unmounting inputs doesn't reset/clear them.
3 participants