no-multi-asterisks rule

[brettz9]

feat: no-multi-asterisks rule to prevent multiple asterisks with middle delimiters or at end of blocks

Fixes #199 (other fixes have now been merged).

[golopot]

I think "ban multiple asterisks at line start" should be a special case of "require one space after asterisk".

/**
 ** @param a  // require one space after asterisk
 *@param b // require one space after asterisk
 */

[brettz9]

Can you please clarify?

[golopot]

Since the potential rule "require one space after leading asterisk" would included the functionality of this pr and do more, it looks like a better solution.

[golopot]

Heuristically, what I want is to enforce the style of leading asterisks, instead of banning a particular occurrence of **.

[brettz9]

Enforce the style to what exactly? One space vs. what? No spaces and a fixed number of spaces?

While I can see allowing the parser to accept it in other styles or bad form, do a lot of projects actually use anything more than a single space in a consistent way? The spec, TS, Closure, etc., all seem, as I can recall, to just use just the one style.

[golopot]

Enforce the style to what exactly? One space vs. what? No spaces and a fixed number of spaces?

Yes I mean the one style.

[brettz9]

So you mean ensure there is one space even if not multiple asterisks--but enforce no other style, right?

[brettz9]

I suggest taking a look at my edit of #199 (comment) to ensure it clarifies what you want.

[brettz9]

I think what you are asking for is pretty much the expectation of check-line-alignment with either the "never" or "always" option.

[brettz9]

If it wasn't clear, I mean that that is how check-line-alignment already behaves.

[golopot]

Ok

[brettz9]

Are you ok with my going ahead with this (and the other PRs), or do you need more time to review?

[gajus]

🎉 This PR is included in version 34.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀