Darren Schroeder 61544eecd6 add version and path to plugin executable help (#13764) ... # Description This change allows one to see the version of their plugin file without trying to register it.  # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use toolkit.nu; toolkit test stdlib"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. -->		2024-09-03 12:46:36 -05:00
..
plugin	add version and path to plugin executable help (#13764)	2024-09-03 12:46:36 -05:00
lib.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
test_util.rs	Split the plugin crate (#12563)	2024-04-27 12:08:12 -05:00