Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Vetur doesn't support @typedef in JSDoc #844

Closed
3 tasks done
ffxsam opened this issue Jul 19, 2018 · 1 comment
Closed
3 tasks done

Vetur doesn't support @typedef in JSDoc #844

ffxsam opened this issue Jul 19, 2018 · 1 comment
Labels
integ:typescript
Milestone
March 2019

Comments

@ffxsam
Copy link

ffxsam commented Jul 19, 2018 •
edited
Loading

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ

Info

  • Platform: macOS 10.13.6
  • Vetur version: 0.12.5
  • VS Code version: 1.25.1

Problem

.vue files do not recognize valid JSDoc syntax (using @typedef to define types).

See reproduction repo below. Basically, when I type getAudiences(, IntelliSense shows options as being of type any, which is incorrect. However, if you import this function in a regular .js file, you'll see it shows ApiOptions, and it's possible to trigger auto-suggest which shows the individual ApiOptions properties, too.

Example in .vue file:

image

Example in .js file:

image

Reproducible Case

https://github.com/ffxsam/vetur-jsdoc-bug
@octref
Copy link
Member

octref commented May 10, 2019

Seems fixed together with upgrading TS in #1163:

image

@octref octref closed this as completed May 10, 2019
@octref octref mentioned this issue May 10, 2019
Closed
@octref octref added this to the March 2019 milestone May 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
integ:typescript
Projects
None yet
Milestone
March 2019
Development

No branches or pull requests
2 participants
@octref @ffxsam