nushell/crates/nu-command/src
Xoffio 82ac590412
Progress bar Implementation (#7661)
# Description

_(Description of your pull request goes here. **Provide examples and/or
screenshots** if your changes affect the user experience.)_

I implemented the status bar we talk about yesterday. The idea was
inspired by the progress bar of `wget`.
I decided to go for the second suggestion by `@Reilly`
> 2. add an Option<usize> or whatever to RawStream (and ListStream?) for
situations where you do know the length ahead of time

For now only works with the command `save` but after the approve of this
PR we can see how we can implement it on commands like `cp` and `mv`

When using `fetch` nushell will check if there is any `content-length`
attribute in the request header. If so, then `fetch` will send it
through the new `Option` variable in the `RawStream` to the `save`.
If we know the total size we show the progress bar 

![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg)
but if we don't then we just show the stats like: data already saved,
bytes per second, and time lapse.

![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg)

![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg)

Please let me know If I need to make any changes and I will be happy to
do it.

# User-Facing Changes

A new flag (`--progress` `-p`) was added to the `save` command 
Examples:
```nu
fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip
fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip
open main.zip --raw | save --progress main.copy
```

# 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
-
I am getting some errors and its weird because the errors are showing up
in files i haven't touch. Is this normal?

# 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.

Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-10 20:57:48 -05:00
..
bits Further cleanup of Span::test_data usage + span fixes (#7595) 2022-12-24 07:41:57 -06:00
bytes Fix typos by codespell (#7600) 2022-12-26 02:31:26 -05:00
charting Fix typos by codespell (#7600) 2022-12-26 02:31:26 -05:00
conversions Further cleanup of Span::test_data usage + span fixes (#7595) 2022-12-24 07:41:57 -06:00
core_commands Continue and Break on Try/Catch (#7683) 2023-01-05 21:41:51 +01:00
database Standardise the use of ShellError::UnsupportedInput and ShellError::TypeMismatch and add spans to every instance of the former (#7217) 2022-12-23 01:48:53 -05:00
dataframe let start open anything and everything (#7580) 2023-01-03 10:47:37 -08:00
date Add extra_usage messages for subcommand-only commands (#7594) 2022-12-24 07:16:29 -06:00
deprecated Remove math eval command (#7284) 2023-01-04 23:50:18 +01:00
env Fix an example of env command (#7603) 2022-12-26 16:40:34 +08:00
experimental Change instances of Value::string("foo", Span::test_data()) to Value::test_string("foo") (#7592) 2022-12-24 10:25:38 +01:00
filesystem Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
filters [Chore] cleanup in where implementation (#7679) 2023-01-04 22:50:02 +01:00
formats Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
generators Further cleanup of Span::test_data usage + span fixes (#7595) 2022-12-24 07:41:57 -06:00
hash Add extra_usage messages for subcommand-only commands (#7594) 2022-12-24 07:16:29 -06:00
math Remove math eval command (#7284) 2023-01-04 23:50:18 +01:00
misc Add more input/output type annotations (#7532) 2022-12-21 20:20:46 +01:00
network Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
path Further cleanup of Span::test_data usage + span fixes (#7595) 2022-12-24 07:41:57 -06:00
platform Fix typos by codespell (#7600) 2022-12-26 02:31:26 -05:00
random Add extra_usage messages for subcommand-only commands (#7594) 2022-12-24 07:16:29 -06:00
shells Add more input/output type annotations (#7532) 2022-12-21 20:20:46 +01:00
strings Improve wording of str replace help messages (#7708) 2023-01-10 20:46:50 +01:00
system Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
viewers Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
default_context.rs Url encode to escape special characters (#7664) 2023-01-05 19:24:38 +01:00
example_test.rs Make stream info visible to users in describe (#7589) 2023-01-03 21:08:05 -08:00
input_handler.rs Standardise the use of ShellError::UnsupportedInput and ShellError::TypeMismatch and add spans to every instance of the former (#7217) 2022-12-23 01:48:53 -05:00
lib.rs Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
progress_bar.rs Progress bar Implementation (#7661) 2023-01-10 20:57:48 -05:00
sort_utils.rs Further cleanup of Span::test_data usage + span fixes (#7595) 2022-12-24 07:41:57 -06:00