Skip to content

Improvement: more consistent exception types #24

@sabberworm

Description

@sabberworm

Currently, misconfigured hops sometimes throw either a NullPointerException, a HopperException or an IllegalArgumentException (or something else entirely). We should try to unify the exception types we use.

Proposal: only throw HopperExceptions for cases where ConflictResolution.THROW is used. All other problems should throw other types of exceptions. IMHO we should go with IllegalArgumentException when we can statically determine that a hop is misconfigured. Other problems should raise the proper exception that is encountered at runtime.

Discuss!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions