Boolean intellisense
See original GitHub issueIntellisense is great for things like typeof
, so why not make it great for boolean types too!
I think adding intellisense for booleans saves a bit of typing, and it still hasn’t been implemented.
Look at this:
const a = (): boolean => true;
a() === // [true, false] intellisense prompt
const b = a();
if (b === /* [true, false] intellisense prompt*/)
I think this would be a great addition to Intellisense. Any feedback is appreciated.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Intellisense doesn't suggest boolean values - Visual Studio Feedback
A function has a boolean parameter. When I write a call to the function and press 't' on the parameter, intellisense suggests everything...
Read more >Visual Basic IntelliSense - Visual Studio (Windows)
When a statement will refer to a Boolean , IntelliSense displays a true-false drop-down menu. Completion can be turned off by default by ......
Read more >VS Code Intellisense when input boolean value #3834 - GitHub
Hi, when input boolean value intellisense does not show the right value for true or false. the value considered as text value.
Read more >VSC - IntelliSense marks boolean operator as errors
IntelliSense is incorrectly marking boolean operators ( and , or , etc.) As errors. Here is an example: enter image description here.
Read more >Boolean Functions in VBA
Code VBA IntelliSense makes these function accessible under submenu VBA , see screenshot. intellisense menu with boolean functions .
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 FreeTop 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
Top GitHub Comments
Apart from loose equality, why would you write either
instead of the following?
Probably the best UX upside is that if you write
if (foo() ===
thinkingfoo
returned some other type, you’d seetrue
/false
in the completion list and immediately know what was up