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.

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

Props are not completed until component tag is closed #1884

Closed
brunnerh opened this issue Feb 20, 2023 · 1 comment · Fixed by #2631
Closed

Props are not completed until component tag is closed #1884

brunnerh opened this issue Feb 20, 2023 · 1 comment · Fixed by #2631
Labels
bug Something isn't working limitation Constraints of the existing architecture make this hard to fix

Comments

@brunnerh
Copy link
Member

brunnerh commented Feb 20, 2023

Describe the bug

In VS Code, props are not completed until the tag is closed.
This is a bit inconvenient as it does not match the typical order of operations, which for me at least is:

  • <ComponentName
  • Possibly auto-import the component
  • Set various properties
  • >

Reproduction

  • Add a component file component.svelte
    <script>
      export let value;
    </script>
    {value}
  • Import and write <Component val in another file
  • Check completions

Expected behaviour

Property value is suggested and nothing else.

System Info

  • OS: Windows 10, 64bit
  • IDE: VSCode

Which package is the issue about?

Svelte for VS Code extension

Additional Information, eg. Screenshots

Open:
image

Closed:
image

@brunnerh brunnerh added the bug Something isn't working label Feb 20, 2023
@jasonlyu123
Copy link
Member

This is a limation we have. See #1302 (comment) for the reason

@jasonlyu123 jasonlyu123 added the limitation Constraints of the existing architecture make this hard to fix label Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working limitation Constraints of the existing architecture make this hard to fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants