Ejected theme folder breaking vscode TS intellisense
See original GitHub issue“react”: “16.8.6”, “react-native”: “0.60.4”, “native-base”: “^2.13.4”, No Expo
After ejecting the theme as mentioned in this link https://docs.nativebase.io/Customize.html#theaming-nb-headref Following code is breaking VSCode Typescript intellisense.
import getTheme from '../../theme/components';
const theme = getTheme();
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:12 (2 by maintainers)
Top Results From Across the Web
TypeScript Programming with Visual Studio Code
IntelliSense shows you intelligent code completion, hover information, and signature help so that you can write code more quickly and correctly. TypeScript ......
Read more >VS Code's Typescript IntelliSense breaks every time I `git ...
I think what's happening is when Eslint runs, it uses one (or more) of the tsconfig.json files, depending on the changed files' location....
Read more >Tailwindcss Suggestions not working in react-app : WEB-48464
I have the same issue, no Tailwind completions for Next.js project using Typescript in WebStorm 2022.2.3. All required plugins are installed and active....
Read more >VS Code Can Do That?
VS Code can refactor promises in TypeScript into Async/Await. ... Use the Breadcrumbs feature in VS Code to quickly jump between folders, files...
Read more >JavaScript Projects (jsconfig.json) - vscode-docs
Visual Studio Code uses the TypeScript language service to make authoring JavaScript ... indicates that the directory is the root of a JavaScript...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
A quick fix for me was to just change the StyleProvider snippet to:
<StyleProvider style={getTheme(material as any)}>
Hope that helps.
Any word on an official fix coming for this?
Having to do a separate file with theme vars that I can never open or my IDE blows up is a pretty bad solution.