fix(tests): decode percent-encoded spaces in test suite paths (#350) - #374
Open
KunalSoyane wants to merge 1 commit into
Open
fix(tests): decode percent-encoded spaces in test suite paths (#350)#374KunalSoyane wants to merge 1 commit into
KunalSoyane wants to merge 1 commit into
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes #350 by properly decoding percent-encoded characters (e.g., %20 for spaces) when resolving file paths across test suites.
Root Cause
Accessing .pathname directly on a URL instance leaves URL percent-encodings intact. When the repository resides in a directory with spaces in its path, Node's fs functions fail with an ENOENT error.
Changes
Replaced direct .pathname string access with fileURLToPath from node:url in command-injection and skills-hardening test files.
Related Issues
Closes #350