Repository navigation
refactor(settings): use time intervals for durations - #176
Merged
Merged
Conversation
esphynox
force-pushed
the
refactor/use-time-interval-for-durations
branch
from
October 15, 2026 18:12
46e46d2 to
c4b762b
Compare
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
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.
Summary
Use
TimeIntervalfor keyboard fade timing and mouse visualizer durations instead of the graphics-orientedCGFloattype. Add a clampedStoredDescriptor.timeIntervalpath and remove redundant conversions across settings view models and animation consumers.Existing UserDefaults keys and double-backed persisted values remain unchanged.
Tests
tuist generatexcodebuild test -project Keyty.xcodeproj -scheme Keyty -destination 'platform=macOS'Run project commands from
Apps/Keyty.UI Changes
N/A
Documentation
Release Notes
N/A