Skip to content

subpath: parsing stops after segments are clear #449

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.

Sign up for GitHub

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

Closed
jkowalleck wants to merge 1 commit into from
+3 −2
Closed

subpath: parsing stops after segments are clear #449

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions purl-specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -492,8 +492,9 @@ To parse a `purl` string in its components:
- Percent-decode each segment
- Discard any ‘.’ or ‘..’ segment from that split
- UTF-8-decode each segment if needed in your programming language
- Join segments back with a ‘/’
- This is the `subpath`
- This list of path segments is the ``subpath``

@jkowalleck jkowalleck Oct 1, 2025

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont concat or further handle the segments, similar to qualifiers.
https://github.com/package-url/purl-spec/blob/main/purl-specification.md?plain=1#L515

- You may escape these path segments if needed by your environment (operating system, file system, programming language, shell, etc)
- You may join these path segments with the path delimiter of your environment (operating system, file system, etc)

- Split the `remainder` once from right on ‘?’

Expand Down