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

Autocomplete fallback #74

Merged
merged 3 commits into from
Nov 5, 2019
Merged

Autocomplete fallback #74

merged 3 commits into from
Nov 5, 2019

Conversation

frenic
Copy link
Owner

@frenic frenic commented Oct 31, 2019

The problem with autocomplete having | string with string literals seems to work just perfectly in VSCode just by replacing string and number with (string & {}) / (number & {}). Suggested in #73.

But is this "hack" safe? Is it really this easy? We need to be sure that Typescript won't give us a type error when some compile options are enabled or they fix a bug that suddenly breaks the hack.

Fixes #8 #73

@frenic frenic added this to the Version 3 milestone Oct 31, 2019
@frenic frenic force-pushed the autocomplete-fallback branch 2 times, most recently from c8281b7 to 2bf4e9c Compare November 3, 2019 19:31
@frenic frenic changed the base branch from next to async-everything November 3, 2019 19:31
@frenic frenic force-pushed the autocomplete-fallback branch from 2ba1cb3 to b0ef126 Compare November 3, 2019 20:33
@frenic frenic force-pushed the autocomplete-fallback branch from b0ef126 to 172d690 Compare November 5, 2019 08:27
@frenic
Copy link
Owner Author

frenic commented Nov 5, 2019

I guess this should be safe since string also is an object. Added tests against this case and if something happens in the future I guess we'll know about it.

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

Successfully merging this pull request may close these issues.

1 participant