You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consider whether InfoChainGenerator should be extensible #87
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.
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.
Activity
gselzer commentedon Sep 6, 2023
Yeah, I think it should be. Theoretically, if someone makes a new
OpInfoimplementation, we will want to make a newInfoChainGenerator. With that said, in scijava/incubator#90 we moveInfoChainGeneratorinto SciJava Ops Engine, so it would be less exposed that way.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.
Merge pull request #87 from scijava/scijava/incubator/remove-wildcard…