Update stack / list: ETag not updated
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Describe the bug
Within the Android Deck app, we use the REST-Endpoints to fetch data from the server using ETags. When a User changes the name of a list, the ETags don't seem to get updated, so our Android client only gets notified, when the user also changes a card within the list.
See this: https://github.com/stefan-niedermann/nextcloud-deck/issues/861
To Reproduce
Steps to reproduce the behavior:
- WebUI: change list name
- Android: pull to refresh
- Name of the list won't get updated
- WebUI: change a card in same list
- Android pull to refresh
- changed card and list both get updated
Expected behavior
On list-update, the etags of the list and the board should be updated
Client details:
see here: https://github.com/stefan-niedermann/nextcloud-deck/issues/861
CC: @stefan-niedermann
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
Reproduce the issue by renaming a list in the WebUI, refreshing the Android client, then changing a card and refreshing again. Trace the REST response ETags for the list and board during these steps; done means both ETags change after a list rename so the Android client receives the new name without a card update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- api, backend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100