Add ReferenceManyInput field about react-admin

[fzaninotto]

I think we should NOT reuse <ReferenceInput>, because that would add too many ifs to the code, and make its API confusing. Instead, create a <ReferenceManyInput> and a <SelectManyInput>.

[fzaninotto]

We have plans to make admin-on-rest as awesome as ng-admin. No, even more.

But it will take months. We need all the help you can give.

The chip input seems OK for an array value, but for references you need autocomplete. I don't see anything of acceptable quality in material UI land, do you have other ideas?

I'm closing this one as we won't open one issue for every ng-admin feature that needs to be ported. Feel free to continue the discussion about the implementation even though the issue is closed.

[fnberta]

This chip input component actually supports autocomplete. If you go to the demo storybook and select "with auto complete, open on focus", you actually get a similar experience to what is now in ng-admin. I hope I'll find the time this week to take a closer look.

[fzaninotto]

Reopening this one as it'll guide us for future enhancements.

[leesei]

Alas, I need this one also.
Guess that'll be another PR 🎉 .

[kimkha]

@fzaninotto Can I add material-ui-chip-input to aor dependencies and make PR? I'm happy to help, but I wonder what is the true way to do that kind of thing.

[fzaninotto]

@kimkha Yes, it's a small dependency, no problem. Could you and @leesei coordinate efforts?

[leesei]

@kimkha I haven't started on it yet but I'll implement it before mid-April.
Are you free to start it now?

[kimkha]

I'm OK to start now, but I think it take time to start, because I'm new with AOR :)

Which function should we support? Array values, reference to many,... what's more?

[leesei]

I suppose <ReferenceManyInput> will bind to a array of ids to source.
I'm not sure if we need a <SelectManyInput>/<MultiSelectInput>.

[kimkha]

Currently, we have <ReferenceManyField>. I think we must separate to 2 inputs: <ReferenceManyInput> for reference, and <ArrayInput> for array only. Because they look like difference...

The first thing, we must handle API calling, and when user choose one, we need to insert the ID of item. But in case of second one, we just only insert the text.

[kimkha]

I change my mind. I think we should re-use <ReferenceInput>, but its children is <ArrayInput>. That might be easy to implement and make AOR better reusable.

[kimkha]

@fzaninotto What do you think about that idea? If yes, I need to change <ReferenceInput> in fetchReferenceAndOptions to add crudGetMany...

[kimkha]

DONE. I will make PR.

[darksonic37]

This should be closed, the change has been merged for a while now, no?

[fzaninotto]

Right, fixed in #597