Generated schema for eslint/max-len can be optimized

[Shinigami92]

The generated file for eslint/max-len can be optimized.

The rule has 3 times the same pattern.
Instead of generating a config and option type, we can reuse the setting type.

[Julien-R44]

Could also be done using an AST

However I wonder if it is worth it. Do you think it's really worth it to optimize this? These are auto-generated files not really made for reading, and for the end user, it doesn't change anything, he will always have the auto-completion of his types despite the interface is duplicated several times.

By introducing a method with AST to remove duplicates, it makes us more code to maintain and we risk introducing bugs.

That said, it's an interesting thing to do.

What do you think about it?

[Shinigami92]

What do you think about it?

⬇️

That said, it's an interesting thing to do.

😄