You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
I've been working on various benchmarks for styled components, emotion, glamorous, etc in VS Code and the defs for glamorous tend to be too verbose -- at least for me.
Due to them going to a second page and just generally taking up a ton of space, it sometimes inhibits keyboard usage. For instance, if you press the down arrow while that tooltip is open, it gets captured and pages down the giant list of available properties instead of going to the next line.
I definitely appreciate types being provided, but perhaps they could be slimmed a bit?
The text was updated successfully, but these errors were encountered:
hey @probablyup, the parameter hints are definitely a bit much for some parts of the typings.
I've got the following setting in my vscode user settings which means I rarely see them, but it would be great to simplify some.
{
"editor.parameterHints": false
}
One of the easy wins here would be to use interfaces instead of types where possible. A few places where types are used were simply to cut down on the work of writing the same things over and over.
I've been working on various benchmarks for styled components, emotion, glamorous, etc in VS Code and the defs for glamorous tend to be too verbose -- at least for me.
Due to them going to a second page and just generally taking up a ton of space, it sometimes inhibits keyboard usage. For instance, if you press the down arrow while that tooltip is open, it gets captured and pages down the giant list of available properties instead of going to the next line.
I definitely appreciate types being provided, but perhaps they could be slimmed a bit?
The text was updated successfully, but these errors were encountered: