mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 14:35:52 +03:00
[GH-ISSUE #69] Show update status on console #43
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#43
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 @muesli on GitHub (Mar 9, 2018).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/69
Updating all bookmarks from the console with
shiori update -ycan take some time if you've stored hundreds or thousands of them. Currently shiori seems to update them all and only then prints out the results to the screen.It would be nice if it could continuously update the progress. Maybe even display a nice little progress bar? Checkout https://github.com/muesli/goprogressbar for some inspiration.
@RadhiFadlillah commented on GitHub (Mar 12, 2018):
Hi @muesli, I've added progress bar while fetching new content in commit 5b36d4.
BTW I also fix the slow update process in commit 9d025dc. This problem is happened because I forgot to put update queries inside the transaction. Now the update should be a lot faster than before.
@muesli commented on GitHub (Mar 18, 2018):
Looks nice!