mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #1167] lower precison for % numbers in error messages #778
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#778
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @m4rtini2 on GitHub (May 17, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1167
Describe the feature you'd like to request
This is not about a real feature request but more a cosmetic enhancement with a low priority.
After the addon got updated i got a failsafe error with a very precise percent number of bookmarks that would get deleted. Like 50.0147815138971%
Describe the solution you'd like
A integer number might be sufficient to signal the severity of the problem.
Describe alternatives you've considered
Leave it as it is. It does no harm. This would be just cosmetic.
@marcelklehr commented on GitHub (May 17, 2022):
Good point, I had the same thought once, but forgot about it.
@marcelklehr commented on GitHub (May 17, 2022):
@pinpontitit This may be a good first issue to tackle if you're up for it :) (This is the relevant code:
github.com/floccusaddon/floccus@9843b9166f/src/lib/strategies/Default.ts (L1679))@github-actions[bot] commented on GitHub (May 22, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.