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'm not sure if this is an LSP issue or an extension issue, but auto-completion doesn't work for package prefixes.
For example, if I have a protobuf message at foo.v1.Bar, typing foo. doesn't present the v1 package. Subsequently, typing foo.v1., doesn't present the Bar option.
However, if I type B.., Bar will show up as an option and will auto-complete to the full path when you hit <TAB>.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is an LSP issue or an extension issue, but auto-completion doesn't work for package prefixes.
For example, if I have a protobuf message at
foo.v1.Bar
, typingfoo.
doesn't present thev1
package. Subsequently, typingfoo.v1.
, doesn't present theBar
option.However, if I type
B..
,Bar
will show up as an option and will auto-complete to the full path when you hit<TAB>
.The text was updated successfully, but these errors were encountered: