Print YAML configuration in output of rules command

[SimplyDanny]

I wonder if this is actually worth a separate swiftlint config [--default] <rule> command? 🤔

[SwiftLintBot]

	17 Messages
📖	Linting Aerial with this PR took 1.12s vs 1.13s on main (0% faster)
📖	Linting Alamofire with this PR took 1.47s vs 1.47s on main (0% slower)
📖	Linting Brave with this PR took 8.39s vs 8.41s on main (0% faster)
📖	Linting DuckDuckGo with this PR took 4.13s vs 4.14s on main (0% faster)
📖	Linting Firefox with this PR took 9.81s vs 9.88s on main (0% faster)
📖	Linting Kickstarter with this PR took 10.63s vs 10.62s on main (0% slower)
📖	Linting Moya with this PR took 0.59s vs 0.61s on main (3% faster)
📖	Linting NetNewsWire with this PR took 3.18s vs 3.19s on main (0% faster)
📖	Linting Nimble with this PR took 0.78s vs 0.78s on main (0% slower)
📖	Linting PocketCasts with this PR took 8.36s vs 8.36s on main (0% slower)
📖	Linting Quick with this PR took 0.38s vs 0.38s on main (0% slower)
📖	Linting Realm with this PR took 11.92s vs 11.94s on main (0% faster)
📖	Linting Sourcery with this PR took 2.4s vs 2.39s on main (0% slower)
📖	Linting Swift with this PR took 5.07s vs 5.1s on main (0% faster)
📖	Linting VLC with this PR took 1.43s vs 1.42s on main (0% slower)
📖	Linting Wire with this PR took 8.71s vs 8.73s on main (0% faster)
📖	Linting WordPress with this PR took 12.55s vs 12.57s on main (0% faster)

Generated by 🚫 Danger

[mildm8nnered]

I wonder if this is actually worth a separate swiftlint config [--default] <rule> command? 🤔

So not arguing against the concept, but I actually had my eye (but not my heart set) on configure as a new command for a Periphery style configuration wizard - see #4898 and #5041 - happy to pick an alternative, but if we had config and configure, that would potentially be a bit confusing.

[SimplyDanny]

I wonder if this is actually worth a separate swiftlint config [--default] <rule> command? 🤔

So not arguing against the concept, but I actually had my eye (but not my heart set) on configure as a new command for a Periphery style configuration wizard - see #4898 and #5041 - happy to pick an alternative, but if we had config and configure, that would potentially be a bit confusing.

Good point. My idea is to offer a way to append a default configuration for a rule to the .swiftlint.yml file like swiftlint config <rule> >> .swiftlint.yml. However, I also see this could be added to the rules command by adding two new options to it:

• --config-only to print only the rule's configuration as YAML
• --default to use the rule's default configuration (instead of what's configured) wherever it is printed

I think the --default also makes sense without the --config-only option for this command.