Fix unit test, by adding a fixed restrict key for pgdump output comparison #233
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
|
|
Collaborator
|
This is blocking other development, so I am forward fixing in a separate PR off of your branch. Your authorship on the initial contribution is still tracked, and you should be added to the list of contributors! Sorry about that! |
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.
Description
Fix unit test, by adding a fixed restrict key for pgdump output comparison
Motivation
To get unit tests to pass
Without this fix, cmd/pg-schema-diff/apply_cmd_test.go fails because the restrict key defaults to a random guid, and won't match when comparing two different pgdump outputs
Testing
go test