op version 2 (2.1.0 in my testing) appends a
\x0a or ASCII newline character to the end of the byte stream when calling
op document get.
I've run a few tests with versions 1.12.4 and 2.1.0. In each case I get the errant byte on the end with version 2, and not with version 1. I've attached a few screenshots. In the screenshots are two example documents each being retrieved by
op version 1.12.4 and version 2.1.0. In each the bytes are piped to
hexdump to show the errant
\x0a byte on the end (or the absence of the byte).
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
I guess technically it's the ASCII "linefeed" not "newline"
Thanks for reporting this @zcutlip ,
I've created an internal issue to fix this bug!
Awesome. Thank you!
Glad to help, @zcutlip! Let us know if you encounter any other bugs/have any feedback on the CLI, overall!
This appears fixed in v2.3.0. Thanks!
Thanks for the valuable feedback!