fix(usage): allow string to be used next to enums #197
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
matthv
previously approved these changes
Mar 14, 2024
jbarreau
changed the title
jbarreau
force-pushed
the
allow_string_in_enums
branch
from
21eab4c
to
bb20d18
Compare
matthv
previously approved these changes
Mar 19, 2024
jbarreau
force-pushed
the
allow_string_in_enums
branch
from
5f12324
to
f4e2112
Compare
matthv
approved these changes
Mar 22, 2024
forest-bot
added a commit
that referenced
this pull request
Mar 22, 2024
## [1.6.1](v1.6.0...v1.6.1) (2024-03-22) ### Bug Fixes * **usage:** allow string to be used next to enums ([#197](#197)) ([1dee475](1dee475))
|
🎉 This PR is included in version 1.6.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
The point is to allow users (and the documentation) to avoid making imports.