nextcloud / nextcloud/files_lock
Support external CIFS storages locked via third-parties via direct access
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 48
Description
Hello
We use Nextcloud to connect to external CIFS-storages. Primary we work on the files in Windows-Explorer. Additionally we can access all files in Nextcloud.
In this case we miss a functionality, that nextcloud does recognize a file-lock coming from Windows-Explorer (opened XLSX-/DOCX-files etc.). That means, in nextcloud I have no idea, when someone is working an files by using direct CIFS-access. So then I would also expexct to see a lock-icon in Nextloud, to provent working in parallel on the same file.
Additionally it would be great the other way. That means, that users working in Explorer get a warning-message, when someone locked the file in Nextcloud or maybe has opened the file in Nextcloud in Collabora-/Onlyoffice.
Thanks
René
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
The issue names external CIFS storage, Windows Explorer, Nextcloud, XLSX/DOCX files, and Collabora/OnlyOffice, but no repository files, tests, or entry points. Start by mapping how locks are represented for direct CIFS access and Nextcloud access; done would require agreed behavior for displaying and warning about locks in both directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100