-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add explain
that collates metadata
from plugins in a pipeline
#818
Closed
5 tasks done
Tracked by
#761
Labels
core-only
This issue is reserved for the IF core team only
Milestone
Comments
zanete
added
draft
The issue is still being written, no need to respond or action on anything.
core-only
This issue is reserved for the IF core team only
labels
Jun 11, 2024
zanete
changed the title
Add
Add Jun 11, 2024
explainer
feature that collates metadata
from all the plugins in a pipeline and either enriches the initialize
info or adds a new block.explainer
that collates metadata
from plugins in a pipeline
@manushak @narekhovhannisyan please review ac to confirm you're ok with it |
zanete
changed the title
Add
Add Jul 15, 2024
explainer
that collates metadata
from plugins in a pipelineexplain
that collates metadata
from plugins in a pipeline
Merged
9 tasks
zanete
removed
blocked
The issue is blocked and cannot proceed.
draft
The issue is still being written, no need to respond or action on anything.
labels
Jul 16, 2024
@jmcook1186 please take a look at the comment on the PR |
@narekhovhannisyan please review 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why: Sub of #761
What: Add
explain
feature that collatesmetadata
from all the plugins in a pipeline and reports it in a newexplain
blockBlocked by:
params.ts
and related logic from IF #814Context
In #815 we are adding parameter metadata as a property of the initialized plugin instance that is set during the plugin initialization. The
explain
feature will list out the metadata for every initialized plugin in the manifest.It should be triggered simply by passing a boolean to
explain
in the top level manifestcontext
, e.g.If any other value is passed to
explain
the feature should not execute.Scope of work:
Acceptance criteria
explain
feature exists in IF and takes a boolean fromcontext
GIVEN the feature exists
WHEN I run the following manifest:
THEN the following block would be added to the outputs, above the
tree
:explainer
is anything other thantrue
, the feature is NOT executedexplain
simply reports it as empty, e.g.The text was updated successfully, but these errors were encountered: