I'm not hugely fond of the name "EngineAware", but...
# development
h
I'm not hugely fond of the name "EngineAware", but I don't have any ideas I like better off the top of my head; wanted to get other peoples' opinions. if we're going to change this name it would be good to do so before 2.0
đź‘Ť 2
h
I was thinking DynamicReturnValue and DynamicParameter Ik it’s similar to the dynamic UI, but that might not be the worst thing. These concepts (workunits) are closely related To me, the key point of this type is that you can dynamically add info the work unit, rather than relying on static things
w
Introspectable
,
Display
,
Rendered
, etc
đź‘Ť 1
(…introspection isn’t really it, but yea: something about logging/rendering/visualizing)
agreed re: renaming.
@hundreds-breakfast-49010: i wouldn’t worry about it as a priority though… plugin stability isn’t until
2.$something
h
Agreed, but simple changes we can make now to avoid lots of rewriting for plugin authors is worthwhile, imo. And it helps us to document what these things are if the name reflects what we’re taking about
đź‘Ť 1
w
folks should not be writing plugins outside the repo if it can be helped. but yes.
h
yeah actually doing this renaming will be a very quick change that's very easy to slip in before 2.0 proper; the harder part is deciding what the name should be
I kind of like
Introspectable
, but that doesn't really cover things like
artifacts
or
level
, that exist to change the workunit
w
Reportable
maybe
đź‘Ť 1