Skip to content
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

Open
Rogerotti opened this issue Aug 21, 2018 · 6 comments
Open

PropTypes provided for Stateless Functional Components #61

Rogerotti opened this issue Aug 21, 2018 · 6 comments
Assignees

Comments

@Rogerotti
Copy link

🐛 bug report

When I try to export component at the end of the .jsx file the intellisense doesn't work.

pic1

To Reproduce

Steps to reproduce the behavior:

  1. Create stateless component or normal with export at the end of the file
  2. The intellisense doesn't work.

🤔 Expected Behavior

Intellisense should work

😯 Current Behavior

pic2

Environment

  • OS: Win 10 x64
  • VS Code Version 1.26.1
@Rogerotti
Copy link
Author

Also please check what happen if you add constructor to a class. I think that might not work either.

@kv4sha
Copy link
Contributor

kv4sha commented Aug 28, 2018

@Rogerotti ok I'll check

@elkinjosetm
Copy link

What's the status of this bug? It's been almost a year and its still open...

@abrantes01
Copy link

abrantes01 commented Nov 16, 2019

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 ?

@eastcoastcoder
Copy link

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.

@amaau
Copy link

amaau commented Jun 26, 2021

What's the status of this bug? It's been almost a year and its still open...

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants