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
This issue is for swiftformat:disable:next. I hope there will be more flexible disable rules, such as disable:this and disable:previous.
Consider the following code:
structDBModel:Codable{/// Some descriptive notes /// swiftformat:disable:next redundantRawValuesenumColumns:String,CodingKey{/// Descriptive comment for the case, with or without it.case id ="id"}}
The situation of swiftformat:disable:next redundantRawValues is awkward. It is mistakenly written into the type annotation of Columns, but if this method is not used, the only option is to use the more complicated swiftformat:disable redundantRawValues, which takes up more lines and is not concise enough.
If we had swiftformat:disable:previous , things would be much better:
structDBModel:Codable{/// Some descriptive notes enumColumns:String,CodingKey{// swiftformat:disable:previous redundantRawValues/// Descriptive comment for the case, with or without it.case id ="id"}}
Sincerely hope that disable:this and disable:previous can be introduced into SwiftFormat.
The text was updated successfully, but these errors were encountered:
As far as I know, there are currently several ways to disable SwiftFormat in the code:
This issue is for
swiftformat:disable:next
. I hope there will be more flexible disable rules, such asdisable:this
anddisable:previous
.Consider the following code:
The situation of
swiftformat:disable:next redundantRawValues
is awkward. It is mistakenly written into the type annotation ofColumns
, but if this method is not used, the only option is to use the more complicatedswiftformat:disable redundantRawValues
, which takes up more lines and is not concise enough.If we had swiftformat:disable:previous , things would be much better:
Sincerely hope that
disable:this
anddisable:previous
can be introduced into SwiftFormat.The text was updated successfully, but these errors were encountered: