-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement coder module #925
Comments
Not sure I understand. Would that be the first time that two non-core modules actually depend on each other (see #386 (comment))? Why wouldn't you want to remove the methods in |
Hmm, that's a good point. I hadn't thought of that added complication for the backwards compatibiilty. Maybe that's enough to not do it and "fix it in documentation" instead? From a user perspective I'd still prefer backwards compatibility, but I definitely hear you on the technical difficulties. Maybe we should start out with an
and then officially split them a bit later down the track when we feel we have time to maintain "stuff that has changed from version x to y that you need to be aware of" notes? |
A software that is properly released usually has some deprecation policy based on a release plan in place. We don't have that and would have to rely on time-based deprecation. That would/could mean we create the new module, copy the methods and add a deprecation note to the docs for |
I can leave the old code in crypto with a |
https://golang.org/pkg/encoding/hex/ |
Addition of encoder module with base64 and hex encode/decode as per #925
Done |
@TerryE Thank you for this, I really want to get rid of the lua implementation of fromBase64() in my code. |
Yes, it is possible and sooner or later I will. There are a number of other modules that were merged into the |
One of these days we'll get a chance to rework how the whole module inclusion system works, and hopefully to something the cloud builder automatically picks up on. |
Implement
coder
module with methods:Denormalise
crypto
to call the coder.toXXX routines. Discussion on #486 refersThe text was updated successfully, but these errors were encountered: