Loosen TypeVar name pattern #5983
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
cdce8p
added
Bug 🪲
Needs backport
andyholmes
added a commit
to andyholmes/valent
that referenced
this pull request
Mar 26, 2022
Pierre-Sassoulas
removed
the
Needs backport
Pierre-Sassoulas
pushed a commit
that referenced
this pull request
Mar 26, 2022
|
Thanks for the quick fix @cdce8p. Don't have much time this weekend, but good to see this is already released! |
andyholmes
added a commit
to andyholmes/valent
that referenced
this pull request
Mar 26, 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.
Description
Allow TypeVar names with multiple uppercase characters like
HVACModeTandIPAddress. Note that if a uppercase suffix is added, it must beT.IPAddressUis still invalid.Closes #5981
/CC: @DanielNoord