-
Notifications
You must be signed in to change notification settings - Fork 340
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
Brackets fix for all failed tests sections #667
Brackets fix for all failed tests sections #667
Conversation
…github.com/ahadalioglu/junit-plugin into brackets-fix-for-all-failed-tests-sections
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.
Inconsistent with #661—should call Util#rawEncode
on each component of the path internally within getRelativePathFrom
as suggested in #664 (comment).
Although we used To address this, I modified the As a result, the encoded URL now preserves the slashes while ensuring that each component is safely encoded. Please review it at your earliest convenience. |
Where is the code for that method? |
Oh, sorry, I have missed that:
However, I believe it would be better to revert to using rawEncode and hope it works this time. |
It is done by using Slashes will now also be encoded. Therefore, I propose temporarily replace only the slashes. |
Now, it's ready with my above-mentioned changes. Additionally, I have another solution:
Please let me know your thoughts. |
As stated in #667 (review) the solution should be consistent with #661 by encoding any characters that need to be encoded, not just square brackets. To accomplish this, the |
Testing done through Jenkins: https://ci.jenkins.io/job/Plugins/job/junit-plugin/job/PR-664/
After the fix implemented in PR #661, the "All Failed Tests" sections continued to fail due to the lack of percent-encoding for square brackets specifically.
This PR addresses and resolves the issue.
Submitter checklist