(Per this gist, excess padding is safely ignored. More tips and tricks in that link).
A Sublime user can work around this by manually typing in the padding before using this feature, but I think adding this redundancy could benefit the overall ease of use (and hopefully not break anyone's workflow).
Base64 Decode will not decode strings with the padding characters removed.
As the padding characters are technically not required to decode without ambiguity, many applications strip the padding after encoding.
A quick fix would be to change the following line (here):
to this:
(Per this gist, excess padding is safely ignored. More tips and tricks in that link).
A Sublime user can work around this by manually typing in the padding before using this feature, but I think adding this redundancy could benefit the overall ease of use (and hopefully not break anyone's workflow).