-
Notifications
You must be signed in to change notification settings - Fork 38k
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
Pass filename hint to the ResourceDecoder #22267
Comments
Thanks for your proposal.
Also, if we decide to do something here, are we talking only about |
FWIW there is similar logic in the converter equivalent: Lines 89 to 98 in 4fdfa42
I suppose we could pass a filename hint without having the |
Feature parity between converters and codecs would be nice, so I add this improvement request in our 5.2 bucket. @filiphr If you need that with 5.1, you can probably wrap the decoder and decorate the resource as a temporary workaround. |
You were faster than me to resolve everything 😄.
I was indeed thinking about passing the filename in the hints, not making the
I was thinking about I actually need the
Thanks for adding it to the 5.2 bucket. Just my 2 cents, you might want to support passing the
I'll look into on our side to see what would be the best approach. Thanks for the hint |
Currently the
ResourceDecoder
uses theByteArrayResource(byte[])
constructor. However, usually when working withResource
theContent-Disposition
header can be used to send the filename of the resource. I think that in this case it would be helpful if that can be passed as the description.The text was updated successfully, but these errors were encountered: