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

Linters Gone Wild #15

Merged
merged 1 commit into from
Dec 19, 2021
Merged

Linters Gone Wild #15

merged 1 commit into from
Dec 19, 2021

Conversation

BuckeyeCoder
Copy link
Contributor

This PR is a bit different. Let's think about all the kinds of changes that can be made, and then divide them into two groups as follows:

  1. Changes that I wrote; we'll call these "substantive" changes;
  2. Changes coming from the Markdown linter I am using; we'll call those "linter" changes.

With those definitions in place, I will tell you that I wasn't 100% pleased with the last PR. The quality was fine, but it was a challenge for me to see the substantive changes I made because they were swallowed up in all the noise emanating from the linter changes. Instead of the GitHub merging process showing us the small, "surgical strikes" that my edits usually are, it was deleting entire paragraphs and then replacing them simply because it wanted to replace triple back-ticks with single back-ticks.

I would rather have a much quieter merging experience, wouldn't you?

So, that spawned the idea for this PR. This is an entire PR dedicated solely to the Markdown linter! There is not even one substantive change in this entire PR. If its been changed, the linter did it; I am blameless lol.

Now, be assured that I have still code reviewed each linter change here. If its here then I have agreed to it, albeit sometimes with a smirk. You're going to see the following:

  1. Genuine errors being corrected. This includes the code back-tick issue;
  2. The linter being very opinionated, even to the point of being a bit ridiculous.

A common example of the second point is when using italics. There are two perfectly valid forms in Markdown for making a word italic: single asterisks and single underscores. Why there needs to be two I don't know, but there are. For no reason — other than having an opinion — this linter changes asterisks to underscores. Does it hurt anything? No. But it certainly makes for a lot of changes when the author preferred asterisks when writing, thus my smirking.

By giving the linter a chance to get its chattiness over with, future PR's will be much quieter with near 100% substantive changes. This PR is an investment towards a quieter, more studious future. — DW

@jonegil jonegil merged commit 90ed108 into jonegil:main Dec 19, 2021
@jonegil
Copy link
Owner

jonegil commented Dec 19, 2021

Good idea to take all ine one.

jonegil added a commit that referenced this pull request Feb 20, 2023
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.

2 participants