tslint.json should have exactly the same options as offered on the command line

[gotofritz]

Bug Report

• TSLint version: 4.4.1
• TypeScript version: 2.1.6
• Running TSLint via: both angular-cli and node_modules/tslint/bin/tslint using tslint.json and tsconfig.json

When I pass a formatter as a command line option then it works
node_modules/tslint/bin/tslint --config ./tslint.json --project ./src/tsconfig.json -t verbose

When I put the formatter in the tslint.json, it doesn't seem to pick it up.
node_modules/tslint/bin/tslint --config ./tslint.json --project ./src/tsconfig.json

I raised a bug about it #2226 , and a contributor said it isn't possible. But most CLI tool offer exactly the same options as arguments or in a config file, it makes no sense to have them different. Normal practice is that either can be used, and if both are presents the command line overrides the config file.

I use tslint via angular-cli and I can't pass any command line options. I would like to be able to use it out of the box. Thanks

[JoshuaKGoldberg]

Removing Ignoring the Type: Breaking Change label per #4811. Now accepting PRs!

[JoshuaKGoldberg]

☠️ TSLint's time has come! ☠️

TSLint is no longer accepting most feature requests per #4534. See typescript-eslint.io for the new, shiny way to lint your TypeScript code with ESLint. ✨

It was a pleasure open sourcing with you all!

[JoshuaKGoldberg]

🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖

🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋