fix(Working Time): precision for percentage fields (backport #16)#17
Merged
barredterra merged 1 commit intoversion-14from Oct 17, 2025
Merged
fix(Working Time): precision for percentage fields (backport #16)#17barredterra merged 1 commit intoversion-14from
barredterra merged 1 commit intoversion-14from
Conversation
(cherry picked from commit f9d1d69)
barredterra
approved these changes
Oct 17, 2025
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
1 participant
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.
After frappe/frappe#34238, percent values are formatted correctly and respect the specified precision or fall-back to the Float Precision according to System Settings.
In this case, we want less precision.
This is an automatic backport of pull request #16 done by Mergify.