David Anson

Makes sense, thanks!

Based on your scenarios, a single rule that runs a user-configurable RegExp against the link destination seems sufficient.

Not today, but a new rule could do this.

I am open to the idea, yes! I would prefer to be consistent across the two projects. However, you will see that this project‘s implementation of the rule already offers...

Having looked at the Ruby PR a little more, I think it would be ideal to support the proposed behavior in addition to allowing sentence-based wrapping as referenced in the...

I think one challenge is how to configure the rule. The Node implementation already has `strict` and `stern` booleans. The first made sense to add that way and the second...

> Did you mean strict and stern booleans? Yes, sorry for the typo. > If I understand this correctly, you propose changing not_wrapped to single in the existing PR? Right....

> > Did you mean strict and stern booleans? > Yes, sorry for the typo. I’ve corrected this in my post above to avoid confusing anyone else.

Can you please clarify the part about “prevents adopting markdownlint”? You can allow tabs in code blocks.

Yes, in the context of the feature you are requesting, tabs would not be required in code blocks. But that should not prevent you from using markdownlint - it’s more...