Skip to content

Better error management #9

@sylvinus

Description

@sylvinus

We need user-friendly error messages in all possible failure scenarios:

  • API is down
  • API is up but Elasticsearch is down: use a proper HTTP error
  • Unexpected JavaScript error: make sure we do fall back to the static version?
  • Whole Go server is down: configure custom error pages in CloudFlare?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions