ResolveInput Hook for File field not saving data correctly

[mherrema]

Bug report

Describe the bug

When using the File field type on a list along with the resolveInput hook, data isn't being saved correctly, resulting in some fields being blank in the admin ui.

To Reproduce

1. Create a list that uses the File field type (using local file in my case)
2. Add a resolveInput hook to the field as follows:

hooks: {
         resolveInput: ({ resolvedData, }) => resolvedData
}

3. Upload a file/item to that list (I tested with an mp3 file)
4. See a blank field listed for the file name

Expected behaviour

The file field should allow the resolveInput hook to manipulate (or simply return in this case) the resolvedData object and save the file correctly and display the file name.

Screenshots

System information

• OS: macOS
• Browser: Chrome

[Falbana]

Hi, I encoutered the same problem, turns out that if you use the resolveInput hook inside the file field (not after the fields), you have to return only the input file and not resolvedData (resolvedData contains all the data, not only the file)
file: {
...
hooks: {
resolveInput: async ({ resolvedData }) => {
var fileInput = resolvedData.file;
...
return fileInput;
}}}

Hope it helped

[mherrema]

Interesting, I'll give that a try, thanks. Maybe this will prompt an update to the documentation then.

[ra-external]

That's it, see #2508

[stale]

It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :)

[bladey]

Keystone 5 has officially moved into active maintenance mode as we push towards the next major new version Keystone Next, you can find out more information about this transition here.

In an effort to sustain the project going forward, we're cleaning up and closing old issues such as this one. If you feel this issue is still relevant for Keystone Next, please let us know.