Skip to content

Decide how to support logging errors and warnings #13

@gselzer

Description

@gselzer

Many ops in the old imagej-ops framework, such as this one or this one attempt to log errors or warnings. Sometimes this is in place of throwing some RuntimeException (as in the case of the former) or other times it is just saying something about the data (as in the case of the latter). We need to find a consistent way to deal with the situations in which we would like to pass on messages/errors.

Regardless of the option, no messages should be allowed as secondary outputs.

Potential solutions:

  • Use Scijava's Logger
  • Create dedicated error subclasses (although this will only solve the issues with errors, not with the logging)
  • Not allow any sort of logging

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions