You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was modeling after TS's path complete, but I guess for html it's a bit different since you can import from folder and it defaults to index.js, and there is no such behavior in html.
A folder path is also valid in HTML (once navigated there, it's up to the web server to decide what to return), but I'd think it's the less common case and it users would rather continue to enter a path.
I would want to hear more people's feedback before doing this. Current behavior is in-line with TS and the two most popular path completion extensions:
Testing #44460
Version 1.21.0-insider
Commit 9a04587
Date 2018-03-01T06:47:39.037Z
foo.html
,bar.html
in a folder 'a/b/c'and do code completion after
/
.a
<a href="../a/"
(slash at the end) and reopen code completion again so that the user can continue completingThe text was updated successfully, but these errors were encountered: