-
Notifications
You must be signed in to change notification settings - Fork 6
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
PropTypes provided for Stateless Functional Components #61
Comments
Also please check what happen if you add constructor to a class. I think that might not work either. |
@Rogerotti ok I'll check |
What's the status of this bug? It's been almost a year and its still open... |
Looks like I've the same problem too. IntelliSense isn't working with class with export at the end. @kv4sha do you have any news on this ? |
Modern React paradigms favor functional components, whether stateless or with hooks, and this extension would be killer if it just supported the new style. I haven't had a reason to write a class based component in almost a year or so since the advent of hooks. Anyone out there willing to take this on? I don't want the overhead of adding Flow or Typescript to my project if this can be accomplished in a more vanilla way. |
+1 |
🐛 bug report
When I try to export component at the end of the .jsx file the intellisense doesn't work.
To Reproduce
Steps to reproduce the behavior:
🤔 Expected Behavior
Intellisense should work
😯 Current Behavior
Environment
The text was updated successfully, but these errors were encountered: