nextcloud / nextcloud/richdocuments
Migrate static mimetype list to dynamic discovery via WOPI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Right now the list of supported mimetypes is maintained statically in the app, which means it can drift from what the connected Collabora/document server actually supports. Whenever upstream adds or drops a format, we have to update the hardcoded list by hand.
The WOPI /hosting/discovery endpoint already advertises the supported actions and their associated mimetypes/extensions, so we should source the list from there instead of hardcoding it.
This will also benefit connecting other office suites via WOPI that may have a different subset of supported mimetypes.
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 where the static supported-mimetype list is defined and how the WOPI /hosting/discovery endpoint is currently accessed. Replace the static source with discovery data, and verify that the resulting list follows the connected document server and supports different WOPI office suites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100