Is there a way to have a install_crate depedency for init tasks/plugins

[wmmc88]

I have an init task that uses a cargo-make plugin to invoke rust-script. Is there a way to enforce that rust-script is actually insatlled (like install_crate = { crate_name = "rust-script", min_version = "0.30.0" })? It seems that either install_crate doesnt work for init tasks, or it doesnt get executed before the plugin.

[wmmc88]

On second thought, is it because for tasks that specify plugins, you're supposed to handle the execution yourself, so it doesn't actually do anything with the install_crate? Is the only way to parse that install_crate section myself in the plugin code and execute it?

[sagiegurari]

@wmmc88 sorry for late answer

1. line numbers - right, its because i put some extra code before yours. for example to exit with error on any error as by default duckscript will not stop on error (like shell scripts don't by default)
2. getting the install crate info -

• task.as_json gives you the entire task data as json
  so you can do
  taskjson = json_parse ${task.as_json}

holds the data -> taskjson.install_crate

• there are other vars that help. see https://github.com/sagiegurari/cargo-make#plugin-sdk

[sagiegurari]

@wmmc88 did it answer you?

[wmmc88]

yes, I understand how it works now. Thank you!

It would be nice if line numbers were synced to actual lines in the code, or there was a way to match the error line to the script line somehow(Does the duckscript get saved in a file somewhere where the lines would match?).

It would also be nice if there was a way to defer to the default behaviour somehow in the plugin. For example, sometimes I want to have a plugin that just adds a little extra processing, but still want all the nice things that cargo make provides for me (dependency installation, min version checking, etc.) without needing to reimplement every single feature in the duckscript for the plugin

[sagiegurari]

Does the duckscript get saved in a file

no. since its embedded inside cargo-make, the script is in memory....
i could dump it via verbose to outside if that helps (maybe i already do that, can't remember)

It would also be nice if there was a way to defer to the default behaviour somehow in the plugin

cm_plugin_run_custom_task enables you to modify the task and run it.
it handles all logic except dependencies, because dependencies should have already been executed so i don't want to execute them again. well, unless i forgot how it works lol