Patch/#159 default tag bug

[Dan503]

This fixes issue #159

[Dan503]

FYI, I tried implementing the solution they gave in the answer to this open issue:
syavorsky/comment-parser#155

It didn't work. It also broke a bunch of other tests so I'm going to steer away from it.

[hosseinmd]

Seem option 2 is better, prettier default using double quotes, Unless singleQuote defined by the user in prettier options

[Dan503]

@hosseinmd can you take another look?

I've resolved all feedback.

I decided it wasn't worth trying to support @default {{ object: 'value' }} with the { ... } as boilerplate wrapped around the value.

The official jsDoc spec says that if there is going to be boilerplate wrapped around the value then it would be @default [{ object: 'value' }] with [ ... ] being the boilerplate.

So with this PR I'm supporting both of these formats:

• @default value - a lean version that VS Code supports
• @default [value] - official jsDoc format with [ ... ] as boilerplate around the default value

I'm not supporting @default {value} though since it's difficult to support and there isn't a strong enough use case behind it.

UPDATE

@default [value] support has been dropped since the documentation just means the value is optional. It doesn't mean you are supposed to wrap the value in square brackets.

[hosseinmd]

I'm not sure about [{}]

jsdoc documented this @default [<some value>] but it doesn't mean to add type inside []

[Dan503]

@hosseinmd ready for another review.

I removed support for the @default [value] format. It only supports the basic @default value syntax now.

I also attempted to implement support for @defaultvalue (all lowercase) but it was being too problematic so I'm dropping it as being out of scope for this PR.