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
Offer an auto-import for unresolved shorthand-named object literal properties #32219
Comments
Can you please share the definition of the |
I'm using createStackNavigator({
screenName,
},{
intialRouteName:'screenName'
}) |
So your code looks something like: export default createStackNavigator({
screenName,
},{
intialRouteName:'screenName'
}) Is that correct? |
Yeap. And I want to auto-import |
Ok sorry, I realize now this is not related to the // a.ts
export const abc = 123; // b.ts
({ abc }); The reason we don't offer suggestion here is because it looks like you are defining a new property. Two actionable things for this issue:
|
Hi, I have the same issue everytime I want to auto-import while using the shorthand syntax using VSCode. |
Hello, I use shorthand-named object properties very often. What if there won't be any suggestions while typing property names, but you can hit |
Is this something you folks might consider adding at some point? I definitely run into this quite a bit. |
suppose I have exported an object called
Foo
infoo.js
, and in another file I want to use something like this:autocomplete will not show
Foo
and of course, will not auto import from that file.to use auto import, I have to write the code like this:
actually autocomplete shows
Foo
, But it doesn't auto import. it hasabc
icon.could you support object shorthand in autocomplete?
The text was updated successfully, but these errors were encountered: