-
Notifications
You must be signed in to change notification settings - Fork 35
Fix: issue with matching null path and relevant test #173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
💡 Verification agent
🧩 Analysis chain
Verify that this URI actually causes parse_url to return false.
The test intent is good, but the URI
'#fragment'might not actually causeparse_urlto returnfalse. It would more likely returnnullfor the path component since fragments are valid URL components.Let me verify the behavior of
parse_urlwith this URI:🏁 Script executed:
Length of output: 1151
Use a URI that actually makes parse_url() return false
PHP’s parse_url('#fragment') does not return
false(it returnsnullfor the path component), so this test never hits the “false” branch. To cover a truly malformed URI, update the test in tests/HttpTest.php (lines 637–648) to something like:Alternatively, if you want to keep
'#fragment', adjust the assertion to reflect thatparse_url()returnsnull/empty path rather thanfalse.🤖 Prompt for AI Agents