Fix a couple of typos in function/class names #145
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
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.
Renames LiteralyEvaluable to LiterallyEvaluable and renames _get_list_attribute_is_member_off to _get_list_attribute_is_member_of.
This does change the API slightly. If users are checking isinstance(redbaron.LiteralyEvaluable) (for example), this change could break them. This is not a documented API, so I assume the guarantee of backwards compatibility does not apply, but if you think it should, we could easily add "LiteralyEvaluable = LiterallyEvaluable" to accept both spellings.