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
The opposite of our current rule that triggers a violation if the same string values as enum member names were used, resulting in redundant duplication, would sometimes be useful if you want to allow refactoring of the Swift API without breaking the API contract.
The text was updated successfully, but these errors were encountered:
This should be a good rule for someone wanting to begin contributing to SwiftLint. RedundantStringEnumValueRule can be used as an inspiration (but I'd expect this one to be actually simpler).
The opposite of our current rule that triggers a violation if the same string values as enum member names were used, resulting in redundant duplication, would sometimes be useful if you want to allow refactoring of the Swift API without breaking the API contract.
The text was updated successfully, but these errors were encountered: