Skip to content

Consistent error handling within the library #117

@emmacunningham

Description

@emmacunningham

Is your feature request related to a problem? Please describe.
Following discussion from #111, we need to agree upon how to consistently handle exceptions within the library. Errors may be the result not just of the downstream developer user but also configuration inputs passed in via a user of the downstream developer's application (for example, a user using some UI to adjust max/min domain).

List of errors that should be surfaced:

  • undefineds returned from d3.extent call in computeContinuousDataDomain

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Kibana Cross Issues

Checklist

  • this request is checked against already exist requests
  • every related Kibana issue is listed under Kibana Cross Issues list
  • kibana cross issue tag is associated to the issue if any kibana cross issue is present

Metadata

Metadata

Assignees

No one assigned

    Labels

    :specsChart specifications related issuediscussTo be discussedenhancementNew feature or request

    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