Repository navigation
feat(web): gauge option for the composer's effort display #26802
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
Open
PedroNavHur
wants to merge
1
commit into
pingdotgg:main
Choose a base branch
from
PedroNavHur:feat/effort-gauge
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+69
−9
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Preserve compatibility with older desktop builds.
If a user selects Gauge in a newer build and then opens an older build, the older
ClientSettingsSchemarejects the entire settings document. Packaged builds share the same settings directory across release channels. The older client then cannot load or save client settings. (raw.githubusercontent.com)Store Gauge in a backward-compatible field, or keep the persisted
effortDisplayvalue valid for older clients.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.
This is true, but I'm leaving it out of this PR. Adding any new choice to a client settings dropdown has the same downgrade problem, because the desktop app decodes
ClientSettingsSchemastrictly (apps/desktop/src/settings/DesktopClientSettings.ts). #26138 recently addednightly-artworkanddev-artworktoEnvironmentIdentificationModethe same way.A separate field just for the gauge would fix this one setting and nothing else. The general fix is to make the settings read tolerate unknown values, for example by falling back to each field's default. That changes how every setting is read, so it should be its own PR rather than part of this one.
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.
@PedroNavHur Understood. A shared settings-read fix belongs in a separate PR. I won’t press for a Gauge-specific field here.
The downgrade risk remains valid but deferred, rather than fixed. The follow-up should verify that an unknown setting value falls back without preventing other settings from loading or saving.
Would you like me to open a GitHub issue for that follow-up?
You are interacting with an AI system.