2023-02-13 13:42:08 +01:00
|
|
|
mod from;
|
|
|
|
|
|
|
|
|
|
use from::{eml, ics, ini, vcf};
|
Add support for engine calls from plugins (#12029)
# Description
This allows plugins to make calls back to the engine to get config,
evaluate closures, and do other things that must be done within the
engine process.
Engine calls can both produce and consume streams as necessary. Closures
passed to plugins can both accept stream input and produce stream output
sent back to the plugin.
Engine calls referring to a plugin call's context can be processed as
long either the response hasn't been received, or the response created
streams that haven't ended yet.
This is a breaking API change for plugins. There are some pretty major
changes to the interface that plugins must implement, including:
1. Plugins now run with `&self` and must be `Sync`. Executing multiple
plugin calls in parallel is supported, and there's a chance that a
closure passed to a plugin could invoke the same plugin. Supporting
state across plugin invocations is left up to the plugin author to do in
whichever way they feel best, but the plugin object itself is still
shared. Even though the engine doesn't run multiple plugin calls through
the same process yet, I still considered it important to break the API
in this way at this stage. We might want to consider an optional
threadpool feature for performance.
2. Plugins take a reference to `EngineInterface`, which can be cloned.
This interface allows plugins to make calls back to the engine,
including for getting config and running closures.
3. Plugins no longer take the `config` parameter. This can be accessed
from the interface via the `.get_plugin_config()` engine call.
# User-Facing Changes
<!-- List of all changes that impact the user experience here. This
helps us keep track of breaking changes. -->
Not only does this have plugin protocol changes, it will require plugins
to make some code changes before they will work again. But on the plus
side, the engine call feature is extensible, and we can add more things
to it as needed.
Plugin maintainers will have to change the trait signature at the very
least. If they were using `config`, they will have to call
`engine.get_plugin_config()` instead.
If they were using the mutable reference to the plugin, they will have
to come up with some strategy to work around it (for example, for `Inc`
I just cloned it). This shouldn't be such a big deal at the moment as
it's not like plugins have ever run as daemons with persistent state in
the past, and they don't in this PR either. But I thought it was
important to make the change before we support plugins as daemons, as an
exclusive mutable reference is not compatible with parallel plugin
calls.
I suggest this gets merged sometime *after* the current pending release,
so that we have some time to adjust to the previous plugin protocol
changes that don't require code changes before making ones that do.
# Tests + Formatting
- :green_circle: `toolkit fmt`
- :green_circle: `toolkit clippy`
- :green_circle: `toolkit test`
- :green_circle: `toolkit test stdlib`
# After Submitting
I will document the additional protocol features (`EngineCall`,
`EngineCallResponse`), and constraints on plugin call processing if
engine calls are used - basically, to be aware that an engine call could
result in a nested plugin call, so the plugin should be able to handle
that.
2024-03-09 18:26:30 +01:00
|
|
|
use nu_plugin::{EngineInterface, EvaluatedCall, LabeledError, Plugin};
|
2023-02-13 13:42:08 +01:00
|
|
|
use nu_protocol::{Category, PluginSignature, SyntaxShape, Type, Value};
|
|
|
|
|
|
|
|
|
|
pub struct FromCmds;
|
|
|
|
|
|
|
|
|
|
impl Plugin for FromCmds {
|
|
|
|
|
fn signature(&self) -> Vec<PluginSignature> {
|
|
|
|
|
vec![
|
|
|
|
|
PluginSignature::build(eml::CMD_NAME)
|
|
|
|
|
.input_output_types(vec![(Type::String, Type::Record(vec![]))])
|
|
|
|
|
.named(
|
|
|
|
|
"preview-body",
|
|
|
|
|
SyntaxShape::Int,
|
|
|
|
|
"How many bytes of the body to preview",
|
|
|
|
|
Some('b'),
|
|
|
|
|
)
|
2023-02-20 16:03:17 +01:00
|
|
|
.usage("Parse text as .eml and create record.")
|
2023-02-13 13:42:08 +01:00
|
|
|
.plugin_examples(eml::examples())
|
|
|
|
|
.category(Category::Formats),
|
|
|
|
|
PluginSignature::build(ics::CMD_NAME)
|
|
|
|
|
.input_output_types(vec![(Type::String, Type::Table(vec![]))])
|
2023-02-20 16:03:17 +01:00
|
|
|
.usage("Parse text as .ics and create table.")
|
2023-02-13 13:42:08 +01:00
|
|
|
.plugin_examples(ics::examples())
|
|
|
|
|
.category(Category::Formats),
|
|
|
|
|
PluginSignature::build(vcf::CMD_NAME)
|
|
|
|
|
.input_output_types(vec![(Type::String, Type::Table(vec![]))])
|
2023-02-20 16:03:17 +01:00
|
|
|
.usage("Parse text as .vcf and create table.")
|
2023-02-13 13:42:08 +01:00
|
|
|
.plugin_examples(vcf::examples())
|
|
|
|
|
.category(Category::Formats),
|
|
|
|
|
PluginSignature::build(ini::CMD_NAME)
|
|
|
|
|
.input_output_types(vec![(Type::String, Type::Record(vec![]))])
|
2023-02-20 16:03:17 +01:00
|
|
|
.usage("Parse text as .ini and create table.")
|
2023-02-13 13:42:08 +01:00
|
|
|
.plugin_examples(ini::examples())
|
|
|
|
|
.category(Category::Formats),
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn run(
|
Add support for engine calls from plugins (#12029)
# Description
This allows plugins to make calls back to the engine to get config,
evaluate closures, and do other things that must be done within the
engine process.
Engine calls can both produce and consume streams as necessary. Closures
passed to plugins can both accept stream input and produce stream output
sent back to the plugin.
Engine calls referring to a plugin call's context can be processed as
long either the response hasn't been received, or the response created
streams that haven't ended yet.
This is a breaking API change for plugins. There are some pretty major
changes to the interface that plugins must implement, including:
1. Plugins now run with `&self` and must be `Sync`. Executing multiple
plugin calls in parallel is supported, and there's a chance that a
closure passed to a plugin could invoke the same plugin. Supporting
state across plugin invocations is left up to the plugin author to do in
whichever way they feel best, but the plugin object itself is still
shared. Even though the engine doesn't run multiple plugin calls through
the same process yet, I still considered it important to break the API
in this way at this stage. We might want to consider an optional
threadpool feature for performance.
2. Plugins take a reference to `EngineInterface`, which can be cloned.
This interface allows plugins to make calls back to the engine,
including for getting config and running closures.
3. Plugins no longer take the `config` parameter. This can be accessed
from the interface via the `.get_plugin_config()` engine call.
# User-Facing Changes
<!-- List of all changes that impact the user experience here. This
helps us keep track of breaking changes. -->
Not only does this have plugin protocol changes, it will require plugins
to make some code changes before they will work again. But on the plus
side, the engine call feature is extensible, and we can add more things
to it as needed.
Plugin maintainers will have to change the trait signature at the very
least. If they were using `config`, they will have to call
`engine.get_plugin_config()` instead.
If they were using the mutable reference to the plugin, they will have
to come up with some strategy to work around it (for example, for `Inc`
I just cloned it). This shouldn't be such a big deal at the moment as
it's not like plugins have ever run as daemons with persistent state in
the past, and they don't in this PR either. But I thought it was
important to make the change before we support plugins as daemons, as an
exclusive mutable reference is not compatible with parallel plugin
calls.
I suggest this gets merged sometime *after* the current pending release,
so that we have some time to adjust to the previous plugin protocol
changes that don't require code changes before making ones that do.
# Tests + Formatting
- :green_circle: `toolkit fmt`
- :green_circle: `toolkit clippy`
- :green_circle: `toolkit test`
- :green_circle: `toolkit test stdlib`
# After Submitting
I will document the additional protocol features (`EngineCall`,
`EngineCallResponse`), and constraints on plugin call processing if
engine calls are used - basically, to be aware that an engine call could
result in a nested plugin call, so the plugin should be able to handle
that.
2024-03-09 18:26:30 +01:00
|
|
|
&self,
|
2023-02-13 13:42:08 +01:00
|
|
|
name: &str,
|
Add support for engine calls from plugins (#12029)
# Description
This allows plugins to make calls back to the engine to get config,
evaluate closures, and do other things that must be done within the
engine process.
Engine calls can both produce and consume streams as necessary. Closures
passed to plugins can both accept stream input and produce stream output
sent back to the plugin.
Engine calls referring to a plugin call's context can be processed as
long either the response hasn't been received, or the response created
streams that haven't ended yet.
This is a breaking API change for plugins. There are some pretty major
changes to the interface that plugins must implement, including:
1. Plugins now run with `&self` and must be `Sync`. Executing multiple
plugin calls in parallel is supported, and there's a chance that a
closure passed to a plugin could invoke the same plugin. Supporting
state across plugin invocations is left up to the plugin author to do in
whichever way they feel best, but the plugin object itself is still
shared. Even though the engine doesn't run multiple plugin calls through
the same process yet, I still considered it important to break the API
in this way at this stage. We might want to consider an optional
threadpool feature for performance.
2. Plugins take a reference to `EngineInterface`, which can be cloned.
This interface allows plugins to make calls back to the engine,
including for getting config and running closures.
3. Plugins no longer take the `config` parameter. This can be accessed
from the interface via the `.get_plugin_config()` engine call.
# User-Facing Changes
<!-- List of all changes that impact the user experience here. This
helps us keep track of breaking changes. -->
Not only does this have plugin protocol changes, it will require plugins
to make some code changes before they will work again. But on the plus
side, the engine call feature is extensible, and we can add more things
to it as needed.
Plugin maintainers will have to change the trait signature at the very
least. If they were using `config`, they will have to call
`engine.get_plugin_config()` instead.
If they were using the mutable reference to the plugin, they will have
to come up with some strategy to work around it (for example, for `Inc`
I just cloned it). This shouldn't be such a big deal at the moment as
it's not like plugins have ever run as daemons with persistent state in
the past, and they don't in this PR either. But I thought it was
important to make the change before we support plugins as daemons, as an
exclusive mutable reference is not compatible with parallel plugin
calls.
I suggest this gets merged sometime *after* the current pending release,
so that we have some time to adjust to the previous plugin protocol
changes that don't require code changes before making ones that do.
# Tests + Formatting
- :green_circle: `toolkit fmt`
- :green_circle: `toolkit clippy`
- :green_circle: `toolkit test`
- :green_circle: `toolkit test stdlib`
# After Submitting
I will document the additional protocol features (`EngineCall`,
`EngineCallResponse`), and constraints on plugin call processing if
engine calls are used - basically, to be aware that an engine call could
result in a nested plugin call, so the plugin should be able to handle
that.
2024-03-09 18:26:30 +01:00
|
|
|
_engine: &EngineInterface,
|
2023-02-13 13:42:08 +01:00
|
|
|
call: &EvaluatedCall,
|
|
|
|
|
input: &Value,
|
|
|
|
|
) -> Result<Value, LabeledError> {
|
|
|
|
|
match name {
|
|
|
|
|
eml::CMD_NAME => eml::from_eml_call(call, input),
|
|
|
|
|
ics::CMD_NAME => ics::from_ics_call(call, input),
|
|
|
|
|
vcf::CMD_NAME => vcf::from_vcf_call(call, input),
|
|
|
|
|
ini::CMD_NAME => ini::from_ini_call(call, input),
|
|
|
|
|
_ => Err(LabeledError {
|
|
|
|
|
label: "Plugin call with wrong name signature".into(),
|
|
|
|
|
msg: "the signature used to call the plugin does not match any name in the plugin signature vector".into(),
|
|
|
|
|
span: Some(call.head),
|
|
|
|
|
}),
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
