-
Notifications
You must be signed in to change notification settings - Fork 513
requireSpacesInsideObjectBrackets using inconsistent terminology #538
Comments
Looking into this |
…and object-brackets in filenames to curly-braces
Can't do this until 2.0 :-( |
Ooops, wrong issue to close |
@markelog @mikesherov Do you want me to add the rule and deprecate it or would that also have to wait until 2.0? Also, when are you planning to have 2.0 out? I will continue trying to help with help-wanted labelled bugs and 2.0 milestones, so let me know if there are any issues you specifically want me to work on. |
I think we could land this as is, although i hope that would not result in a lot of conflicts with 1.x.
There is no dead line.
@mdevils ? |
I'm working on |
@mdevils Keep waiting! Thanks! |
Moving to #1834 - let me know/change it if it's moved over incorrectly. |
The terminology of
requireSpacesInsideObjectBrackets
is inconsistent. The rule refers to "brackets" but the description (and other rules) refer to this character as curly braces.Consider renaming the rule or description to make this more consistent.
The text was updated successfully, but these errors were encountered: