spring-projects / spring-projects/spring-integration
Add "content-type" header population from the AbstractFilePayloadTransformers [INT-3868]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
Artem Bilan opened INT-3868 and commented
There are some use-cases when we need to know the content-type of the payload.
Since AbstractFilePayloadTransformer s transforms incoming File to specific type, it would be better to carry the content-type from there as well.
Similar solution we have in the ObjectToJsonTransformer
No further details from INT-3868
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with AbstractFilePayloadTransformer and compare its payload handling with ObjectToJsonTransformer, as referenced in the issue. Trace the existing transformer tests or entry points from those classes and verify how content type is represented. Done means file payload transformations preserve the payload content-type in the resulting message, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100