nextcloud / nextcloud/calendar
Handle the dav backend returning a 500 error
Open
Nobody has claimed this yet.
1. to develop
enhancement
technical debt
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Is your feature request related to a problem? Please describe.
When the backend returns a 500 error, the calendar simply shows the spinner endlessly.
Describe the solution you'd like
When such an error is encountered, inform the user of the issue.
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 reproducing a DAV backend 500 response in the calendar interface and trace where the loading spinner is managed. The work is done when the error is surfaced to the user and the spinner no longer runs indefinitely; the issue does not name a file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100