nextcloud / nextcloud/cdav-library
Having DavObject::etag property writable
Open
Nobody has claimed this yet.
1. to develop
high
question
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 16
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 9
Description
@skjnldsv Can you please elaborate again why https://github.com/nextcloud/cdav-library/blob/master/src/models/davObject.js#L57 should be writable here?
Etags are only ever generated on the server and can't be set by the client. And updates will only work if the etag in the If-Match header is correct.
Thx :)
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 reading src/models/davObject.js around line 57 and trace where the etag property is read or assigned in the library. Clarify whether client-side writes are intended, then document the decision or define the agreed behavior and verification needed to consider the issue resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100