You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
This lint is excellent and works really well, especially for classes. However, I believe it shouldn’t be applied to extensions at all. Extensions are often grouped and can have varied and distinct names, making it impractical to enforce the same rules as for regular code.
If applying the lint to extensions is necessary, it should at least provide an option to enable or disable it. This flexibility would allow developers to decide whether or not it fits their use case, especially when dealing with extensions heavily.
Proposed Solution:
• Do not apply the lint to extensions by default.
• If that’s not possible, provide a configurable option to enable or disable the lint specifically for extensions.
This change would make the lint more adaptable to real-world scenarios without disrupting common practices like grouping extensions.
The text was updated successfully, but these errors were encountered:
Description:
This lint is excellent and works really well, especially for classes. However, I believe it shouldn’t be applied to extensions at all. Extensions are often grouped and can have varied and distinct names, making it impractical to enforce the same rules as for regular code.
If applying the lint to extensions is necessary, it should at least provide an option to enable or disable it. This flexibility would allow developers to decide whether or not it fits their use case, especially when dealing with extensions heavily.
Proposed Solution:
• Do not apply the lint to extensions by default.
• If that’s not possible, provide a configurable option to enable or disable the lint specifically for extensions.
This change would make the lint more adaptable to real-world scenarios without disrupting common practices like grouping extensions.
The text was updated successfully, but these errors were encountered: