Deprecate tokenize option
#527
Merged
Conversation
This file contains 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
Use `TokenType` instead to determine whether the tokenization is enabled.
Lagovas
reviewed
Apr 14, 2022
Validate `Tokenized`, but do not use it for checks.
36128bb
to
54ec6b5
Compare
Lagovas
reviewed
Apr 15, 2022
Lagovas
approved these changes
Apr 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR deprecates
tokenizefrom encryptor config. It is still present, but it's role is taken bytoken_type- if it's not empty, the tokenization is enabled.Also, forbids the
tokenize: false and token_type: <something>pair.Checklist
with new changes - Deprecate
tokenizationflag product-docs#244CHANGELOG.md is updated (in case of notable or breaking changes)Benchmark results are attached (if applicable)Example projects and code samples are up-to-date (in case of API changes)