Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More readable output when comparing very long strings #13

Open
zkochan opened this issue May 2, 2016 · 1 comment · May be fixed by #14
Open

More readable output when comparing very long strings #13

zkochan opened this issue May 2, 2016 · 1 comment · May be fixed by #14

Comments

@zkochan
Copy link

zkochan commented May 2, 2016

I use tap-diff in mos to test markdown files. Basically mos can generate some parts of the markdown files. The testing part checks whether the generated version matches the current one in the file system.

The markdown files are huge and the output is hard to read. Lets suppose I have renamed my package to mos2 and ran mos test. The output will be hard to read

There are two reasons it is hard to read:

  1. The newlines are displayed as \n instead of actual newlines
  2. There is too much noise, lines that match are included in the output as well.

The output would be a lot more readable, if it would be displayed like in diff-so-fancy

reference: mos/issue#59

@zkochan
Copy link
Author

zkochan commented May 3, 2016

This package does a good output for string diffs https://github.com/HiroakiMikami/pdiff
It can probably be used in tap-diff

zkochan added a commit to zkochan/tap-diff that referenced this issue May 3, 2016
make the comarison between huges strings look better

close axross#13
zkochan added a commit to zkochan/tap-diff that referenced this issue May 3, 2016
make the comarison between huges strings look better

close axross#13
@zkochan zkochan linked a pull request May 3, 2016 that will close this issue
zkochan added a commit to zkochan/tap-diff that referenced this issue Nov 3, 2016
make the comarison between huges strings look better

close axross#13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant