[API-141, API-395] Replace utf with string in public API #345
Conversation
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
As decided with the team, methods containing the word `utf` is renamed with `string`. (`read_utf` -> `read_string` etc.). For backwards compatibility, old methods are still there but we have a deprecation documentation for them.
mdumandag
force-pushed
the
utf-to-string
branch
from
f76e72c to
892c393
Compare
mdumandag
changed the title
degerhz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As decided with the team, methods containing the word
utfisrenamed with
string. (read_utf->read_stringetc.).For backwards compatibility, old methods are still there but we
have a deprecation documentation for them.
Closes #342
Closes #367