Fix --custom-progress to register 0 as a valid input#182
Merged
ErikReider merged 1 commit intoErikReider:mainfrom Nov 21, 2025
Merged
Fix --custom-progress to register 0 as a valid input#182ErikReider merged 1 commit intoErikReider:mainfrom
ErikReider merged 1 commit intoErikReider:mainfrom
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
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.
--custom-progressseems to ignore argument when value is0or0.0. Runningswayosd-client --custom-progress=0would exit with error messageNo args provided....I suspect it has something to do with how GLib handles
0as an argument value when the argument type isDouble.Instead used
Stringand validated the value insidehandle_application_args, consistent with how the other numeric arguments are parsed.New to Rust, sorry if I overlooked something obvious.