`keys` in prefop result items is not correctly returned

[nighca]

When a prefop (e.g., vsample) generates multiple files, the PrefopRet return value of OperationManager.Prefop lacks the items[].keys field data from the HTTP response body. Specifically, PrefopRet.Items.Keys is empty despite the HTTP response body providing its value.

[nighca]

@xgopilot Can you draft a PR to fix this?

[xgopilot]

✅ Pull Request Created

I've successfully created PR #178 to fix the missing keys field issue.

Root Cause

The problem occurred in two places:

1. media/apis/prefop/api.go - The PfopTaskItem struct was missing the Keys field
2. storage/pfop.go - The Prefop() method wasn't copying the Keys field from the API response

Changes Made

File: media/apis/prefop/api.go

• Added Keys []string field to PfopTaskItem struct
• Added JSON tag "keys,omitempty" to jsonPfopTaskItem struct
• Updated MarshalJSON() to serialize the Keys field
• Updated UnmarshalJSON() to deserialize the Keys field

File: storage/pfop.go

• Updated the Prefop() method mapping logic to copy item.Keys to FopResult.Keys

Result

Now when a prefop operation (like vsample) generates multiple files, the PrefopRet.Items[].Keys field will correctly contain all the object names returned by the API.

Pull Request: #178