base64 icon indicating copy to clipboard operation
base64 copied to clipboard

Support for encoding and decoding binary data using a Base64 representation

Results 8 base64 issues
Sort by recently updated
recently updated
newest added

All versions of base64 use `String#unpack1`, introduced in Ruby 2.4. In https://github.com/ruby/base64/pull/17, the gemspec was updated to declare Ruby `>= 2.4` as a dependency, but this change was only published...

Few months back I updated base64 to 0.2.0 with other dependencies and it was working now I upgraded ruby to 3.0.6 and it started giving error `[error.log](https://app.cloud66.com/stacks/live_logs#) — App 227286...

Update docs to remove the conflict between the `Newlines` section and the `Base64.urlsafe_encode64` section regarding the inclusion of newline characters in the encoded output. closes #27

I was reading the current rdocs for Base64, and in the `Newlines` section it says: > An encoded string returned by [Base64.encode64](https://ruby-doc.org/3.3.0/stdlibs/base64/Base64.html#method-i-encode64) or [Base64.urlsafe_encode64](https://ruby-doc.org/3.3.0/stdlibs/base64/Base64.html#method-i-urlsafe_encode64) has an embedded newline character after...

Basically, I hated how I had to write Base64.encode64, it felt so redundant, so I created aliases for every method of this library, to allow for a more simple "Base64.encode"...

Mainly adds explicit `:call-seq:` for each method, to show return value and make argnames more descriptive.

documentation

I'm thinking of building a CLI for `Base64` that would be a classic filter: take input from stdin and put output onto stdout. Later enhancements could add input from files...

enhancement