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

[RFR] New AutocompleteArrayInput #3667

Merged
merged 6 commits into from
Sep 12, 2019
Merged

Conversation

djhi
Copy link
Collaborator

@djhi djhi commented Sep 10, 2019

  • Refactor AutocompleteArrayInput using downshift
  • Refactor common components used by AutocompleteInput
    - [ ] Refactor (hooks, etc.) to avoid too much code duplication between AutocompleteArrayInput and AutocompleteInput To be done in another PR
  • Update documentation
  • Update Upgrade guide

@djhi djhi added this to the 3.0.0 milestone Sep 10, 2019
@djhi djhi changed the title [WIP] New AutocompleteArrayInput [RFR] New AutocompleteArrayInput Sep 11, 2019
Copy link
Member

@fzaninotto fzaninotto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! I love that you used the same code for Autocomplete and AutocompleteArray.

UPGRADE.md Outdated Show resolved Hide resolved
packages/ra-ui-materialui/src/input/getSuggestions.ts Outdated Show resolved Hide resolved
djhi and others added 3 commits September 11, 2019 18:12
Co-Authored-By: Francois Zaninotto <francois@marmelab.com>
Co-Authored-By: Francois Zaninotto <francois@marmelab.com>
@djhi
Copy link
Collaborator Author

djhi commented Sep 11, 2019

Reviewed. Note that I will probably refactor those components a lot along with the others which handle multiple choices in a future PR

@fzaninotto fzaninotto merged commit c082a6c into next Sep 12, 2019
@fzaninotto fzaninotto deleted the autocomplete-array-input-2 branch September 12, 2019 09:03
@mpaciu
Copy link

mpaciu commented Oct 4, 2019

I should write this issue maybe in sandbox, but like is the same problem here reporterted, only i go to mencion it. i am testing the beta 3.0.0 version, and i am seeing that the problem with this component when working with ReferenceInput persist. Attached an image.

In the firs image i typed the letter ka. In the second image i wrote the letters ka an the letter u. When the component filter, the filter value stay on top of the window.

I hope to be clear and to be in the right place.

Sure, thaks you a lot for all this work in this project, is great.

type k
type k and u

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

Successfully merging this pull request may close these issues.

3 participants