-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Support evolving the type with assignments for expando object #12416
Labels
In Discussion
Not yet reached consensus
Suggestion
An idea for TypeScript
VS Code Tracked
There is a VS Code equivalent to this issue
Comments
This has been referenced before in #11839 |
mhegazy
changed the title
IntelliSense does not work for common module pattern
Support evolving the type with assignments for expando object
Dec 15, 2016
mhegazy
added
Suggestion
An idea for TypeScript
In Discussion
Not yet reached consensus
labels
Dec 15, 2016
Is there any intend to fix this issue in the near future????? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
In Discussion
Not yet reached consensus
Suggestion
An idea for TypeScript
VS Code Tracked
There is a VS Code equivalent to this issue
Copied from #12278 (comment)
OP = @abgivant
I use a similar module pattern in an application I'm working on, and the lack of IntelliSense/definitions for those has been an issue for me as well.
Mine follow this basic pattern:
Would it be possible to do something like include an option in the jsconfig.json file to specify a property name or list of names to track when determining module exports?
Maybe something like this?
The text was updated successfully, but these errors were encountered: