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

allow individual styling in multiBar.create() #136

Closed

Conversation

Araxeus
Copy link

@Araxeus Araxeus commented Feb 19, 2023

on multiBar.create(), allow changing the following style options:

  • barCompleteChar
  • barIncompleteChar

Because I just wanted to have a top bar that is a general status, and the other ones are the running processes

gif

on `multiBar.create()`, allow changing the following style options:
* `barCompleteChar`
* `barIncompleteChar`
@AndiDittrich
Copy link
Member

hi @Araxeus ,

thanks for your contribution. i can confirm the behaviour but like to prefer a more comprehensive solution: some more elements of the options initialization has to be moved into the generic-bar constructor. therefore i won't merge your request directly

btw. don't commit changes to meta files like .gitignore

@Araxeus
Copy link
Author

Araxeus commented Feb 19, 2023

btw. don't commit changes to meta files like .gitignore

And why is that?

I'm using yarn v3 and installing creates .yarn and .pnp folders with dozens or hundreds of files

Without adding them to the .gitignore it becomes very painful to commit when I have hundreds of "tracked changes"

Also what reason would there ever be not to modify .gitignore? It's not like it changes the program in any way... Its literally here to make dev life easier

therefore i won't merge your request directly

As you wish, but I personally think that since I spent time on this fix, and you want to use it - it's good etiquette to merge then create a fix commit
(Or merge into a dev branch and fix it before merging to main)

Or you could just tell me what changes do you request, and I'll try doing it myself

@AndiDittrich
Copy link
Member

a pull request should only contain changes to required files..

@AndiDittrich
Copy link
Member

added to 6c75740

@Araxeus
Copy link
Author

Araxeus commented Feb 19, 2023

Anyways, thank you for merging the feature 🎉

I now see that I forgot to also update the auto padding option

@Araxeus
Copy link
Author

Araxeus commented Feb 19, 2023

And i also just wanted to say, if it was my first time contributing to open source, I dont think I would have been very encouraged by the fact that you "discarded" my work

It's not my first rodeo, so I understand where you're coming from, I'm just saying its not a very welcoming behavior

The first pull request I ever made was met with excitement and encouragement, which made me continue on the open source path :)

Just food for thoughts @AndiDittrich

@AndiDittrich
Copy link
Member

sry for this but on the other hand you've to understand that it's very time consuming to give everybody a crash course howto contribute, fix their first time mistakes etc. didn't have time for that...i know that the standard git workflow is complex for beginners.

fixing issues directly is much more efficient especially if other changes needs to be applied. so don't worry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants