✨ add bad linebreaks linter+fixer

[ctcpip]

tests would be nice, if someone wants to have a go 😃 .. otherwise I'll get to it eventually... probably...

[ljharb]

Looks good :-) lots of empty line padding tho, makes it a bit hard to read.

[acutmore]

Thanks @ctcpip! When I was manually regex fixing this I noticed that I got false positive match on code blocks (I had copied some code that the speaker had pasted into Matrix, so the notes would have the relevant context).

Maybe we can detect "```" blocks and ignore them. Long term feels like we should use a proper markdown parser in case there are other cases?

[OnkarRuikar]

Maybe we can detect "```" blocks and ignore them. Long term feels like we should use a proper markdown parser in case there are other cases?

Just a suggestion. May be following could work:
The markdownlint plugin markdownlint-rule-search-replace has capability to narrow scopes to only code or only text. [example code]

Config provided in this discussion will work to flag the hard wrap cases. Auto fixing, for this case, would require a separate script which could get the locations from the logs.

[ctcpip]

Looks good :-) lots of empty line padding tho, makes it a bit hard to read.

sir, please. these are my emotional support linebreaks

[ctcpip]

@acutmore

When I was manually regex fixing this I noticed that I got false positive match on code blocks

ah yes...

```javascript
a = { b: x };
a = ({ b: x });
( { b: x } = a );
( ({ b: x }) = a ); // does not work
```

right now, this code will collapse the first two lines. so in this case, I think the fix to appease this linter will be:

```javascript

a = { b: x };
a = ({ b: x });
( { b: x } = a );
( ({ b: x }) = a ); // does not work
```

not ideal, but an acceptable trade-off. agree implementing this with a proper lexer would be a lot better

[ctcpip]

I've addressed all comments that I'm willing to address 😄

I'll follow on with a PR to fix the linting errors

[ljharb]

also was serious about the excessive blank line paddings :-p