fix: issues with custom enum name in Postgres#7661
Merged
AlexMesser merged 7 commits intomasterfrom May 18, 2021
Merged
Conversation
6 tasks
fixed `enumName` renaming;
|
@AlexMesser Hello, Thank you for fixing this issue. Do you have an idea on when would be the next |
Collaborator
Author
|
@eranganovade we plan to release a new version at the end of this month |
|
Hello, thank you for fixing this issue! Are you still planning the new release with this fix for today? |
Collaborator
Author
|
@PetrBrabec |
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
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 of change
Fixes #7614
Fixes #7647
Pull-Request Checklist
masterbranchnpm run lintpasses with this changenpm run testpasses with this changeFixes #0000