v2.3.3

[2.3.3] 05.12.2019

Thanks to hontas for following changes:

• [Added] Svelte V3: Implement component documentation parsing provided by top level comment in HTML markup or in the JS section, marked with @component JSDoc attribute.

v2.3.2

[2.3.2] 02.12.2019

Thanks to Hostas for following fixes:

• [Fixed] Svelte V3: Improve type parsing for properties with default values.
• [Fixed] Svelte V3: In some cases type property was setup with wrong structure and data, now it fixed.

v2.3.1

[2.3.1] 25.11.2019

• [Fixed] Svelte V3: Fix parsing issues when anonymous functions are used in event handlers at markup (Issue #18)

v2.3.0

Changelog: [2.3.0] 02.10.2019

• [Added] Svelte V3: Implement support of script element locations
• [Fixed] Svelte V3: Fix parsing when component have multiple <script> blocks
• [Added] Spec: Property locations was added to items and presents the list of item code locations
• [Changed] Spec: Property loc for items marked as depricated, see locations property instead

V2.1.0

[2.1.0] 09.08.2019

• [Added] Svelte V3: Implement support for property binding parsing (bind:proprty={...})
• [Added] Svelte V3: Implement support for event parsing which dispatched from code (dispatch(...))
• [Added] Svelte V3: Implement support for event parsing which dispatched from markup expressions (<button on:click="{() => dispatch(....)}">)
• [Added] Svelte V3: Implement support for ref parsing (bind:this={...})
• [Fixed] Spec: Property SvelteDataItem.let changed to SvelteDateItem.kind, that was named as let by mistake

v2.0.0

Implement basic support of svelte v3 syntax parsing

1.1.5

Some fixes with @param and @type parsings

1.1.4

[1.1.4] 07.12.2018

• [Fixed] Fix and refactor param keyword parsing to handle some wrong cases (fix and close issue #7)

v1.1.3

[1.1.3] 03.12.2018

• [Fixed] Improve crash handling in parser logic, now all errors fall into reject(...) method instead throwing up

v1.1.2

[1.1.2] 30.11.2018

• [Fixed] Fix issue when parsing types from JSDoc, cover more cases. Previously type @type {('plain'|'plain-negative')} was not supported in case of - symbol