Move attachment type declaration to backend
Open
Nobody has claimed this yet.
1. to develop
enhancement
technical debt
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
As a intermittent measure, we added the attachment type that is returned from the backend when saving / updating a backend message by looping through all attachments and adding a type local if it isn't set. This should be moved to the backend.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
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 by tracing the backend handling for saving and updating messages, focusing on where attachments are returned and where their type is currently added locally. Done means the backend declares the attachment type consistently for saved and updated messages, so the local workaround is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100