`ETag` is not updated if settings of a board have changed
Open
Nobody has claimed this yet.
1. to develop
backend
bug
feature: api
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
- Check
ETagof a board - Change notification setting
- Expect
ETagto be different from step 1. - it is not.
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 listed steps against a board and trace how the ETag is produced when the notification setting changes. Compare the ETag before and after the update; done means the value differs after the setting change and the original reproduction no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100