Improve reporting when using --report-changed-only#57
Merged
gitlost merged 3 commits intowp-cli:masterfrom Dec 11, 2017
Merged
Conversation
gitlost
approved these changes
Dec 11, 2017
Contributor
|
Thanks @LC43 ! |
danielbachhuber
pushed a commit
that referenced
this pull request
Nov 18, 2022
Fix/report improvement
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
3 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.
when only reporting changes, if a table doesn't have primary keys, don't print any message.
if the content of the table is empty, don't print the headers.
added functional tests for ( using --report-changed-only )
when made 0 replacements, report should be empty
when a tables doesn't have a primary key, report should not contain the skipped table
improvement from #55