Open benjamin-kirkbride opened 1 year ago
Also, I think, that while technically to spec, requiring the preceding dot to represent a "true" FQDN is a battle that is already lost, and is not a hill worth dying on here.
dots were initially conceived, then it was decided hyphens would be prefered.
Yes
hyphens can exist in domain names
This is a good point I hadn't thought of.
requiring the preceding dot to represent a "true" FQDN
The preceding dot was actually not related to FQDN --- it was to prevent an unquoted dotted key from being valid TOML :)
The preceding dot was actually not related to FQDN --- it was to prevent an unquoted dotted key from being valid TOML :)
I see, well as stated above, I'm of the opinion that this would be a feature and not a bug :)
At the top of https://github.com/editorconfig/editorconfig/issues/482 there is an example toolconfig that contains this snippet:
Note the use of dots as separators.
Then below this is said:
Originally posted by @cxw42 in https://github.com/editorconfig/editorconfig/issues/482#issuecomment-1403023825
My assumption is that dots were initially conceived, then it was decided hyphens would be prefered.
My opinion:
com-cool-linter-linelength = 88
com-coollinter-line_length = 88
is not allowed?this will make it very easy for
cool-linter
(the core?), without regex, to check all it's configs.