-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: correct crypto encoding information (v4.x) #7799
Conversation
The default encoding for crypto methods was changed in v6.0.0, with v4.x keeping a default of `binary`. Ref: nodejs#5500 Fixes: nodejs#7712
LGTM |
LGTM. Perhaps the documentation could be explicit about the fact that the default encoding changed in v6? Aside: 'enforced' is a bit of an odd choice of words. |
I’ve updated with “implied” substituted where “enforced” is currently being used. And +1 to being explicit about the change in v6, but that should probably go into a different PR against master. |
@addaleax is this important enough to be rolled into v4.5.0 or could it wait for the next patch release? |
@thealphanerd uff… doesn’t really matter? It can wait, but it’s a only a correction in the docs. |
LGTM |
The default encoding for crypto methods was changed in v6.0.0, with v4.x keeping a default of `binary`. Ref: #5500 Fixes: #7712 PR-URL: #7799 Reviewed-By: Claudio Rodriguez <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in d771d5e |
Checklist
Affected core subsystem(s)
doc
Description of change
The default encoding for crypto methods was changed in v6.0.0, with v4.x keeping a default of
binary
.Ref: #5500
Fixes: #7712