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.

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

Pytest-like progress bar #14

Open
Martmists-GH opened this issue Feb 19, 2018 · 5 comments
Open

Pytest-like progress bar #14

Martmists-GH opened this issue Feb 19, 2018 · 5 comments
Assignees
Labels
enhancement New feature or request Hacktoberfest

Comments

@Martmists-GH
Copy link
Member

No description provided.

@hargoniX
Copy link
Contributor

Do we just say for example if we have 4 linters in config one linter equals 25% or do we actually try to predict the runtime of every linter and then calculate percentage from that?

@Martmists-GH
Copy link
Member Author

image

@hargoniX
Copy link
Contributor

k

@hargoniX
Copy link
Contributor

Could you show us a picture of how you would imagine the progress bar? @Martmists

@Martmists-GH
Copy link
Member Author

Martmists-GH commented Feb 27, 2018

# dashes are the amount of tools to run
# Between brackets is the current being run linter
[----] 0% (flake8)
[P---] 25% (pylint)  # first linter passed
[PF--] 50% (vulture)  # second linter failed

This only happens on one self-editing line (similar to pip and youtube-dl)

@Martmists-GH Martmists-GH added the enhancement New feature or request label Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Hacktoberfest
Projects
None yet
Development

No branches or pull requests

3 participants