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

Bug with optional chaining autocompletion with strictNullCheck enabled #2326

Closed
3 tasks done
victorgarciaesgi opened this issue Sep 25, 2020 · 0 comments · Fixed by #2357
Closed
3 tasks done

Bug with optional chaining autocompletion with strictNullCheck enabled #2326

victorgarciaesgi opened this issue Sep 25, 2020 · 0 comments · Fixed by #2357
Labels
bug integ:typescript lsp:completion

Comments

@victorgarciaesgi
Copy link

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

Info

  • Platform: macOS
  • Vetur version: 0.28.0
  • VS Code version: 1.49

Problem

Normally since TS 3.7 with strictNullCheck: true, VSCode would behave like this when autocompleting a property of a maybe undefined object (in a TS file), and activated by the setting typescript.suggest.includeAutomaticOptionalChainCompletions

Like here

However in a .vue file, this behaviour is happening

post is of type Post | undefined, so it would normally add the ?., but it even removes the .

Bug vetur
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug integ:typescript lsp:completion
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support optional deprecated when completion yoyo930021/vuter
2 participants
@yoyo930021 @victorgarciaesgi