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
As context, specifying a particular range in a file for a rule could be helpful when there are duplicated nodes.
More specifically, a seemingly common pattern in Go is to keep assigning an error to the same identifier.
Currently, there is no easy way to clean up the error handling if statement for the call with enabledFlag in the snippet below.
Matching err != nil would also wrongly match the second if statement.
Providing a line numbers range could be a way to handle cases like this correctly.
As context, specifying a particular range in a file for a rule could be helpful when there are duplicated nodes. More specifically, a seemingly common pattern in Go is to keep assigning an error to the same identifier.
Currently, there is no easy way to clean up the error handling if statement for the call with enabledFlag in the snippet below. Matching err != nil would also wrongly match the second if statement. Providing a line numbers range could be a way to handle cases like this correctly.
Include/Exclude specific (patterns) of files
The text was updated successfully, but these errors were encountered: