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

Fix/remove extra space #141

Merged
merged 3 commits into from
Jan 30, 2021
Merged

Conversation

arthurw1
Copy link
Contributor

@arthurw1 arthurw1 commented Dec 30, 2020

This PR addresses #140

Update

This PR removes all alignment spaces for log level constants.


The change here is simply to revert #135

The extra spaces highlighted in #140 was caused by using \t as delimiter.

Result:
image

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mcollina mcollina requested a review from jsumners December 30, 2020 11:26
@jsumners
Copy link
Member

This is basically creating churn between space formatting and tab formatting. @Zirak introduced space formatting because they found it easier to read the formatted output. @dublx converted it to tab based formatting for more consistency. I think we need a better solution than alternating between these two every few months.

@mcollina
Copy link
Member

@jsumners wdyt? should we land this or not?

@jsumners
Copy link
Member

jsumners commented Jan 21, 2021

@jsumners wdyt? should we land this or not?

I really don't think so. Not until the parties involved that have been interested in this formatting speak up (@Zirak and @dublx).

My opinion is we remove this alignment formatting feature completely if no one is able to propose a solution that works as everyone expects. It seems to me that the issue is down to the terminal emulator and font being used and how they present \t and .

I just don't know how we can satisfy all desires here easily. Reverting the \t change will cause #135 to be an issue again.

@dublx
Copy link
Contributor

dublx commented Jan 21, 2021

Aye, I totally agree.
I'm burned out of time to work on this unfortunately but in terms of choice i'd go with investing time to make \t work well for most people.

@mcollina
Copy link
Member

I think we should revert the feature.

@jsumners
Copy link
Member

@arthurw1 would you like to create a PR that completely reverts the space formatting feature?

@arthurw1
Copy link
Contributor Author

@jsumners Yes I can take that on. I will simply make the changes on top of this current branch if that's ok.

@jsumners
Copy link
Member

That is fine.

@arthurw1 arthurw1 force-pushed the fix/remove-extra-space branch from 6f2bd89 to 6675125 Compare January 27, 2021 14:22
@arthurw1
Copy link
Contributor Author

@jsumners @mcollina PR updated based on latest decision

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Member

@jsumners jsumners left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jsumners
Copy link
Member

@mcollina do we think this is patch, minor, or major? I think I could make an argument for any one of them.

@mcollina
Copy link
Member

I would land this as a minor. If you are parsing this manually you are doing it wrong.

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.

4 participants