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
Thank you for linking those issues @marcelofabri .
I agree for type declarations a padding at the start or end is something many people do.
What we wanted to prevent in our team is code being needlessly bloated by empty lines at the beginning of func or trailing closures.
Not 100% sure how to separate the type declarations from the closure implementations with regex, will try my best.
Example:
So far we have
vertical_whitespace
with themax_empty_lines
parameter.There are plenty of places where empty lines are good to increase grouping.
One thing we have observed though and would like to prevent in our projects are empty lines at the beginning, like in
or
we don't think there is any reason to allow empty lines at the start of methods so I would like to propose a new rule disallowing this.
I'm about to make a PR too, but since I haven't used
sourcery
yet I might need a few minutes to get it right (and make all tests pass).The text was updated successfully, but these errors were encountered: