srp: rename and deprecate legacy implementation#237
Merged
Conversation
Attempts to steer people towards the new RFC5054-compatible implementation by adding `*_legacy` and `Legacy*` to methods and types for the `srp` v0.6-and-earlier compatible implementation. Ideally it can be removed in the next breaking release after this one, and we can only support RFC5054. But for now, this makes a migration possible.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Attempts to steer people towards the new RFC5054-compatible implementation by adding
*_legacyandLegacy*to methods and types for thesrpv0.6-and-earlier compatible implementation.Ideally it can be removed in the next breaking release after this one, and we can only support RFC5054. But for now, this makes a migration possible.