Open
Conversation
Made-with: Cursor
anxinxu
commented
Apr 26, 2026
Author
There was a problem hiding this comment.
@LossyDragon Could a maintainer please approve the workflows for this fork PR? Thanks.
Collaborator
|
If I understand your PR correctly, wouldn't |
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
2 participants
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.
Description
his PR tightens query-string handling when building CDN request URLs in Client (steam/cdn).
Empty query: If the optional query argument is an empty string, it is treated as “no query” and no query parameters are appended (avoids pointless work and odd ?-only URLs).
Leading ?: If the string starts with ?, that prefix is stripped before splitting on &, so callers can pass either foo=bar or ?foo=bar and get the same parsed parameters.
No README or public API changes.
Checklist