Skip to content
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.

Sign up for GitHub

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

Jump to bottom

consider adding progress indicator #118

Open
prototype99 opened this issue Oct 18, 2021 · 2 comments
Open

consider adding progress indicator #118

prototype99 opened this issue Oct 18, 2021 · 2 comments
Labels
Priority: Low Low Priority Type: Enhancement New feature or request on existing feature

Comments

@prototype99
Copy link
Contributor

This would make it clearer when running the software how far it is and how much is left to be done

example of possible output:

Fetching events: [ 40 / 354 ]
Currently fetching for: Python-North-West-Meetup
@Sean12697 Sean12697 added Priority: Low Low Priority Type: Enhancement New feature or request on existing feature labels Oct 19, 2021
@Sean12697
Copy link
Member

If #121 is implemented it might make this feature slightly less useful, although this is still a good idea and should be implemented in either case, the priority has been set to low for this issue due to the differential impact #121 would make.

@prototype99
Copy link
Contributor Author

yeah I can see how that would help. i'd say the benefit post #121 could be helping make sure errors aren't missed in a sea of 'Fetching * for:' that could be put behind a verbose flag though in case people do in fact want that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Low Low Priority Type: Enhancement New feature or request on existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prototype99 @Sean12697