It would be useful to have a extra flag to make sure the output keys is not sorted. Since sometimes,I need to feed it to other cli tool or onlt want sttr to just escape it directly will keeping it,unsorted*.

Adds support for input files. The argument will be checked if it is a file and in that case, it will be read and used as input.

In addition, a default flag is set for the processors so that they can react differently to the input.

I noticed that the hash functions give different outputs when you pipe the input.

> echo "Hello World" | sttr md5
e59ff97941044f85df5297e1c302d260

> sttr "Hello World"
b10a8db164e0754105b7a99be72e3fe5

In the first case, a linefeed is passed with the echo command. I have implemented this so that if the input does not come from a file, the trailing line breaks are removed from the input. I think for simple, single-line inputs, you usually don't want the newline passed into the hash function.

Currently unable to follow the installation guide for installation on macOS 12.1 with Apple M1 because of the following error:

Error: Invalid formula: /opt/homebrew/Library/Taps/abhimanyu003/homebrew-sttr/Formula/sttr.rb
formulae require at least a URL
Error: Cannot tap abhimanyu003/sttr: invalid syntax in tap!

I suppose the error stems from this part in the formulae which seems to support only Intel chips?:

on_macos do
    if Hardware::CPU.intel?
      url "https://github.com/abhimanyu003/sttr/releases/download/v0.2.11/sttr_0.2.11_darwin_amd64.tar.gz"
      sha256 "37f720259894838ccbebf2d2491305f05be47daf3f2a509b2f0b5b06a3f1811f"

      def install
        bin.install "sttr"
      end
    end
  end

@abhimanyu003

go/pkg/mod/github.com/abhimanyu003/[email protected]/cmd/processor_sort-lines.go:40:25

This just happened in the last hour when I was repulling it into a new project.

This version works: go install github.com/abhimanyu003/sttr@e5600168e954fbe603cba134226874b1e81c297a, everything after this fails.

Suggest that might be a good github action for post-merge to flag an install failure

• Adds the ability to read files directly. If the first argument is a file, its content is used as the input (like in tools like cat etc.).
• Changed the parameter type for the transform function to []byte to support building checksums of binary files.
• Unified the naming of the 1st parameter of the transform function, was a mix out of input and data.

I used the file-reading on the README.md, the sttr binary itself and the lazygit binary (commit=50e2ba542264937ead2b9f914c0605acb1ef7924, build date=2021-06-01T16:08:11Z, build source=binaryRelease, version=v0.28.1-next, os=darwin, arch=amd64) and compared it with the results of the tools md5 and shasum (macOS):

This PR improves the template for the generated commands. The timestamp is removed to avoid unnecessary changes when (re)generating the files.

Unfortunately, there are still a few (annoying) trailing tabs in the commands with flags.

This update fixes character counting, which was previously returning the number of bytes rather than the number of runes.

For reference, note that with Latin one character is generally one byte, however other unicode characters (such as East-Asian characters and emojis) can have multiple bytes per character.

|String|Chars|Bytes| |-|-|-| |hi|2|2| |你好|2|6|

Example: https://play.golang.org/p/hWrTqV9HxWb

I would like to see a flag that makes it possible to process the texts directly, without going through the menu. I think this would be quite useful to use the tool e.g. in scripts.

Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

• CircleCI
• TravisCI
• Jenkins
• Other

Added test cases for command.

• alias
• description
• filterValue
• flags
• name
• title.

During this, I found that one command alias was not correct.

PS: I will add more if the format is looking okay.

an overview of standardized paddings is here https://en.wikipedia.org/wiki/Padding_%28cryptography%29

i saw the for 0.2 zero-padding has been merged

this enhancement request would rely upon that capability