Removing additional whitespace

cli/.gitignore

@@ -1,16 +1,16 @@
-# Generated by Cargo
-# will have compiled files and executables
-debug/
-target/
-
-# These are backup files generated by rustfmt
-**/*.rs.bk
-
-# Ignore OpenAPI cache files
-.openapi_cache
-# Ignore generated OpenAPI documentation
-unit-openapi/docs
-# Ignore autogenerated OpenAPI code
-unit-openapi/src
-
+# Generated by Cargo
+# will have compiled files and executables
+debug/
+target/
+
+# These are backup files generated by rustfmt
+**/*.rs.bk
+
+# Ignore OpenAPI cache files
+.openapi_cache
+# Ignore generated OpenAPI documentation
+unit-openapi/docs
+# Ignore autogenerated OpenAPI code
+unit-openapi/src
+
 config

cli/README.md

@@ -1,18 +1,18 @@
 # NGINX UNIT Rust SDK and CLI
 
-This project provides a Rust SDK interface to the 
+This project provides a Rust SDK interface to the
 [NGINX UNIT](https://unit.nginx.org/)
-[control API](https://unit.nginx.org/howto/source/#source-startup) 
+[control API](https://unit.nginx.org/howto/source/#source-startup)
 and a CLI (`unitctl`) that exposes the functionality provided by the SDK.
 
 ## Installation and Use
-In order to build and use `unitctl` one needs a working installation of Maven 
-and Cargo. It is recommended to procure Cargo with Rustup. Rustup is packaged 
-for use in many systems, but you can also find it at its 
+In order to build and use `unitctl` one needs a working installation of Maven
+and Cargo. It is recommended to procure Cargo with Rustup. Rustup is packaged
+for use in many systems, but you can also find it at its
 [Official Site](https://rustup.rs/).
 
-With a working installation of Cargo it is advised to build unitctl with the 
-provided makefile. The `list-targets` target will inform the user of what 
+With a working installation of Cargo it is advised to build unitctl with the
+provided makefile. The `list-targets` target will inform the user of what
 platforms are available to be built. One or more of these can then be run as
 their own makefile targets. Alternatively, all available binary targets can be
 built with `make all`. See the below example for illustration:
@@ -30,7 +30,7 @@ with debug_info, not stripped
 ```
 
 As demonstrated in the example above, compiled binaries may be found in the
-targets folder, under the subdirectory corresponding to the build target 
+targets folder, under the subdirectory corresponding to the build target
 desired.
 
 
@@ -106,7 +106,7 @@ $ unitctl edit
 
 {
   "success": "Reconfiguration done."
-}       
+}
 ```
 
 ### Display interactive OpenAPI control panel
@@ -137,7 +137,7 @@ Timeout waiting for unit to start has been exceeded
 
 We welcome pull requests and issues!
 
-Please refer to the 
+Please refer to the
 [Contributing Guidelines](../CONTRIBUTING.md) when doing a PR.
 
 ## License

cli/build/openapi-generator-cli.sh

@@ -74,5 +74,4 @@ java -ea                          \
   -Xms512M                        \
   -Xmx1024M                       \
   -server                         \
-  -jar ${DIR}/${jar} "$@"
-
+  -jar ${DIR}/${jar} "$@"

cli/man/unitctl.1

@@ -14,7 +14,7 @@ Report any issues on the project issue tracker at:
 \fB<https://github.com/nginx/unit>\fR
 .
 .SH ACKNOWLEDGEMENTS
-WRITE ME 
+WRITE ME
 .
 .SH AUTHOR
 Elijah Zupancic \fB<[email protected]>\fR

cli/unit-openapi/README.md

@@ -408,5 +408,4 @@ cargo doc --open
 
 ## Author
 
-[email protected]
-
+[email protected]

cli/unitctl/src/unitctl.rs

@@ -123,7 +123,7 @@ pub(crate) enum Commands {
             help = "Output format: yaml, json, json-pretty (default)"
         )]
         output_format: OutputFormat,
-    }
+    },
 }
 
 fn parse_control_socket_address(s: &str) -> Result<ControlSocket, ClapError> {