Allow Image Removal through Parent Component.

[talivodworks]

Is your feature request related to a problem? Please describe.
I have a use case, let say I want to upload a file and for some reasons my onDrop function has gone into error state e.g Server responded with error. Now the Image thumbnail is still in the preview list. There is no way I can remove the file from the list or Identify that an error has occurred for that.

import React, {useState} from 'react';
import { ImageInput, ImageField } from 'react-admin';



export const UploadImage = (props) => {
	const [imageId, setImageId] = useState();
	return (
		<ImageInput
			accept="image/*"
			source="profileImage"
			reference="user"
			multiple={true}
			options={
				{
					onDrop: async ([file]) => {
						// Assume this will fail
						try {
							const id = await uploadToServer(file)
							setImageId(id);
						} catch (e) {
							// Remove Image Preview Here...
						}
					}
				}
			}
		>
			<ImageField source="profileImage" />
		</ImageInput>
	)
}

Describe the solution you'd like
I have seen this issue ImageInput keeps adding imagest to state, this works fine. It would be great if we have a way to trigger the removal process through JS (without clicking the remove button)

Describe alternatives you've considered
I can't think of any alternative solution to this issue as the state which is keeping the track of file items is maintain inside the FileInput.tsx

• beforeRender
• InRender

and there is no way to change that state.

[djhi]

Please follow the issue template

[talivodworks]

Please follow the issue template

Before I was not sure which template to follow that is why i tried my best to explain this in well formatted way. But I believe it is more of a feature request so I have followed the new feature template.

Thank you.

[Luwangel]

You're right, it's between a feature and an issue. So I'm labelling this issue as an enhancement.

Have a good day,
Adrien

[WiXSL]

master branch is feature-freeze, but a solution for this has been implemented already in version 4 #7003.
So I'm closing this feature request as it has been implemented.