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.
Initial thoughts, I am wondering if this should actually return True since there was a match -- alternatively, we might handle this on line 780/782:
elif req.link and match.has_metadata("direct_url.json")
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.
Then we check on 772, 780 and 797 the boolean value of
req.link
, which could be done once before and the cut out from there. Maybe that is a style choice.My idea was that if we can not properly compary e.g. that from
I would assume that expected behavour for not being able to make the comparison to
req.link.scheme
should default to False.But yes, thinking about it, it makes more sense to return True, as after the if statements True is also returned by default.