[Bug]: Elvis (?) is breaking autodocs and 'show source' for Svelte components

[silkroadnomad]

Describe the bug

Under a number of circumstances when an Elvis (?) operator is being used, the "autodocs" function stops working and the jsdoc description does not appear inside the storybook properties documentation. Also, the 'show source' function starts delivering incorrect and confusing code.

To Reproduce

I used the Button example of a new Svelte based Storybook installation for simplicity:
See line 14 as an example:

https://stackblitz.com/edit/github-tqvcar?file=src%2Fstories%2FButton.svelte

Furthermore, I realized that "?"- operators inside the Svelte components HTML / Svelte code, lead to the same situation.

Also the description must be before the @type jsdoc command and not after. Otherwise, it does not appear.

System

Environment Info:

  System:
    OS: macOS 13.4.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 18.4.0 - ~/.nvm/versions/node/v18.4.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.12.1 - ~/.nvm/versions/node/v18.4.0/bin/npm
  Browsers:
    Chrome: 116.0.5845.110
    Safari: 16.5.2
  npmPackages:
    @storybook/addon-essentials: ^7.4.0 => 7.4.0 
    @storybook/addon-interactions: ^7.4.0 => 7.4.0 
    @storybook/addon-links: ^7.4.0 => 7.4.0 
    @storybook/blocks: ^7.4.0 => 7.4.0 
    @storybook/jest: ^0.2.1 => 0.2.2 
    @storybook/svelte: ^7.4.0 => 7.4.0 
    @storybook/sveltekit: ^7.4.0 => 7.4.0 
    @storybook/test-runner: ^0.13.0 => 0.13.0 
    @storybook/testing-library: ^0.2.0 => 0.2.0

Additional context

• [Bug] JSDoc prop descriptions aren't added to autodocs addon-svelte-csf#122
• [Bug] Svelte component documentation isn't added to autodocs documentation #23904
• Property descriptions missing from Docs Page on Svelte + TypeScript #15891

[j3rem1e]

This is caused by KatChaotic/sveltedoc-parser#87

sveltedoc-parser fails to parse the component. The documentation is not injected into the source, and we use this documentation to lookup the name of the component. If the documentation is not present, then we call 'component.name'. In the case of the example here, 'component.name' links to the Proxy HMR from vite.