Zxynine / EvenBetterComments

My take on the better-comments extension which incorporates many pull requests and multi tag definitions
https://marketplace.visualstudio.com/items?itemName=Tion.evenbettercomments
MIT License
11 stars 1 forks source link

chore(README): update spacing #15

Open Kosai106 opened 5 months ago

Zxynine commented 4 months ago

Is there a particular reason for going with spaces over tabs aside from it making it more condensed? Is it causing problems for you in any particular way or causing vscode to complain about improper formatting? If it is causing problems I will absolutely consider merging the pull, but if not I think it would be more hassle for me to keep the formatting like that as I prefer to use tabs and so all of my settings enforce tabs which would make it extra work on my end to ensure any changes I make to this file in the future does not introduce tabs back into it and make the formatting inconsistent.

Kosai106 commented 4 months ago

Is there a particular reason for going with spaces over tabs aside from it making it more condensed? Is it causing problems for you in any particular way or causing vscode to complain about improper formatting? If it is causing problems I will absolutely consider merging the pull, but if not I think it would be more hassle for me to keep the formatting like that as I prefer to use tabs and so all of my settings enforce tabs which would make it extra work on my end to ensure any changes I make to this file in the future does not introduce tabs back into it and make the formatting inconsistent.

It's not because anything is broken per say, it's purely to make the REAMDE more readable on GitHub.

I have no preference otherwise, it was just difficult to parse because of the large spacing, see below for example:

image