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

require(...).connect() hint is usually inappropriate #120

Open
SpenceKonde opened this issue Nov 5, 2015 · 1 comment
Open

require(...).connect() hint is usually inappropriate #120

SpenceKonde opened this issue Nov 5, 2015 · 1 comment

Comments

@SpenceKonde
Copy link

Any instance of "require().connect(" in the right hand side of the IDE brings up a tool-tip like popup while typing - and in this case, it's just about always inappropriate.

No matter what module is being called, it suggests 'connect(options,callback) -> socket' - which... which actually isn't ever the case, technically speaking, since even for the WiFi/Ethernet modules, you don't get a socket back...

@gfwilliams
Copy link
Member

Hmm, thanks - this'll be to do with tern, initialised here.

It really needs a special handler making for require - I guess for now we could do something that just forced it not to give a hint.

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

2 participants