Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: The
u == nilcheck is redundant forurl.Parseand can be removed or replaced with a more meaningful guard.url.Parseguarantees a non-nil*url.URLwhenevererr == nil, sou == nilshould never be true and just adds noise/misleading signal. If you want to guard against missing/empty args, validatearg(e.g.arg == "") before callingurl.Parse, and keep the post-parse check as justif err != nil { ... }.Suggested implementation:
}) after this block still match correctly with surrounding code (e.g., whereschemeis used later). You may need to add one more}after the snippet if thisifblock was originally closed later in the function.uanderrare referenced later in the function, you might need to declare them before theif arg == "" { ... }block (e.g.var u *url.URL; var err error) and assign them inside theelseto keep them in scope.