Compare Final Config for Testing

[FSVetaz]

Print out final eslint config with the rules sorted alphabetically. Then it will be compared to the previous reason.

To-Dos

• Run tests (part of pre-push hook)
• Update demo and tests, if linting configuration is being changed
• Update documentation & README
• Increment package.json version

[skye2k2]

The purpose of having the output saved in a readable (multiline) format is so that the humans can see what changed. Shoving everything into one line might make the test output cleaner, but makes the git diff a nightmare.

[skye2k2]

npm test now creates an untracked demo/test/snapshots/new-lint-results.txt-e file with the original content.

Tests almost pass, but new-lint-final-config.json has a developer-specific entry:

"parser": "/home/vetaz/fs-webdev/eslint-config-tree/node_modules/babel-eslint/lib/index.js"

[skye2k2]

I did not like the -e extension added to the output file. Can you test to see if using a .tmp extension breaks in your version of sed?

[FSVetaz]

I did not like the -e extension added to the output file. Can you test to see if using a .tmp extension breaks in your version of sed?

That doesn't work unfortunately.

[skye2k2]

And if it is quoted '.tmp'?

[FSVetaz]

And if it is quoted '.tmp'?

nope. You use FreeBSD? instead of OS X's sed?

[FSVetaz]

Ohh that is interesting

[skye2k2]

Thanks for your diligent work on this. I feel much more secure in making new changes, now.