mirror of
https://github.com/nushell/nushell
synced 2025-01-08 11:18:58 +00:00
11977759ce
# Description This is one of many commands that needs the `input_output_types()` part of the signature filled in so that `$nu.scope.commands` shows the signature properly which leads to the documentation being updated properly. TIL that when commands like `cal` don't have Example tests that can easily be expressed and require the use of `None` results that we need to use this as part of the signature. ```rust .allow_variants_without_examples(true) // TODO: supply exhaustive examples ``` Related to https://github.com/nushell/nushell/issues/7287 # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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. |
||
|---|---|---|
| .. | ||
| cal.rs | ||
| mod.rs | ||
| seq.rs | ||
| seq_char.rs | ||
| seq_date.rs | ||