Missing converter: trailing-comma

[JoshuaKGoldberg]

💥 Missing Converter

• tslint-to-eslint-config version: 1.2.0
• typescript-eslint version: 2.3.2

TSLint Rule Name

trailing-comma

[JoshuaKGoldberg]

The issue here is that this package doesn't know how to convert the TSLint rule into the equivalent ESLint rule. Accepting PRs to add in a converter! 🙌

docs/Development.md has a root overview for how to get started. Within that, docs/Architecture.md#rule-converters talks about how these converters operate. Check the typescript-eslint roadmap to see suggestions on equivalent ESLint rules to convert to.

See #189 for an example of a simple rule converter that was recently added in.

[deerawan]

May I take this one?

[JoshuaKGoldberg]

Go ahead @deerawan! ✨

[deerawan]

@JoshuaKGoldberg I found some variations of TSLint options to be mapped to ESLint one

e.g

{"multiline": "always", "singleline": "never"} // tslint
“always-multiline” // eslint

{ “multiline”: “always”, “singleline”: “always” } // tslint
“always” // eslint

{ “multiline”: “never”, “singleline”: “never” } // tslint
"never" // eslint

{"multiline": "always", "singleline": { “arrays”: “always-multiline” }} // tslint
..... // eslint

and much more

How far do you think we should handle these cases?

[JoshuaKGoldberg]

Sorry @deerawan, I don't quite follow what you're asking?

In general, I think we should aim to get the closest possible mapping of equivalent behaviors... and if it's impossible to get them exactly the same, notices to explain the differences.

[KingDarBoja]

I could go ahead and fix this one if @deerawan is not working on this 🍰

[deerawan]

@KingDarBoja almost finish with it 👍