Improve error handling when FSH Online cannot reach packages.fhir.org
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Transferred from internal JIRA issue originally created 2023-12-21.
Recently, the cert on [packages.fhir.org](http://packages.fhir.org/) was expired and FSH Online could not make requests. When this happened, FSH Online was just spinning like it was still trying to run SUSHI/GoFSH. We probably should have some nicer way for an error to be returned in the console and the spinners to stop saying “couldn’t reach [packages.fhir.org](http://packages.fhir.org/)”.Recently, the cert on [packages.fhir.org](http://packages.fhir.org/) was expired and FSH Online could not make requests. When this happened, FSH Online was just spinning like it was still trying to run SUSHI/GoFSH. We probably should have some nicer way for an error to be returned in the console and the spinners to stop saying “couldn’t reach [packages.fhir.org](http://packages.fhir.org/)”.
Contributor guide
Research direction
Start by tracing the FSH Online request path to packages.fhir.org and the code that controls the SUSHI/GoFSH spinners. Reproduce an unreachable-package scenario, then verify that a console error is returned and the spinners stop instead of continuing indefinitely.
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
- 35/100