RFC: Nonstandard tags that should be processed in "Lax" mode

[aciccarello]

As the strict mode is defined, what things are important to handle in "Lax" mode?

• Unique @tags
• Using @return instead of @returns
• Using @typeparam instead of @param (I haven't seen this but TypeDoc supports it)

[octogonz]

I'm thinking the criteria should be based on tags that either:

1. Have useful information that we wouldn't want to lose (e.g. @returns), or
2. Might cause the comment to be parsed incorrectly if we simply trimmed the tag (e.g. we can safely omit @constructor, but if we omit @throws then what will we do with {InvalidArgumentException} after it?)

IIRC the compiler team approached their implementation empirically, by amassing a large corpus of TypeScript code from GitHub and then analyzing which patterns were most popular. @DanielRosenwasser do you guys have a list of commonly used JSDoc constructs somewhere?

[DanielRosenwasser]

@aozgaa will have some information here.