Skip to content

Consider whether InfoChainGenerator should be extensible #87

Closed
scijava/incubator
#92

Description

@ctrueden

And if so: whether there is ever a possibility of multiple implementations handling the same scenario. As written currently, an exception would be thrown in that case.

Activity

  1. gselzer commented on Sep 6, 2023

    @gselzer
    Member

    Consider whether InfoChainGenerator should be extensible

    Yeah, I think it should be. Theoretically, if someone makes a new OpInfo implementation, we will want to make a new InfoChainGenerator. With that said, in scijava/incubator#90 we move InfoChainGenerator into SciJava Ops Engine, so it would be less exposed that way.

    As scijava/incubator#46 (comment), an exception would be thrown in that case.

    That's a great point, we should fix that logic. I'd like to wait until scijava/incubator#90 is merged, though, to avoid conflicts.

  2. self-assigned this
    on Sep 26, 2023
  3. added this to the 1.0.0 milestone on Sep 26, 2023
  4. added a commit that references this issue on May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions