Tarjei Skjærset

We have the exact same problem. Sad to see no progress on this issue. @DunetsNM how did you work around this?

I agree that this is very jarring and a strange experience in an app that claims to "support macOS".

Hi, thanks for creating the issue! This is definitely a bug. Did I understand correctly that this worked properly in 1.0.7, but broke on 1.0.10? 1.0.10 was IIRC a workaround...

Okay so I've looked into it some more, and this is still the same bug in the TypeScript compiler that version 1.0.10 was meant to work around. I can't seem...

Thanks for the understanding! Having literally any other field on the object fixes it, the only case it breaks is if you have an optional record with only an `optional(string)`....

Hi, thanks for reporting this! I've written a test case to reproduce your problem and can see that I experience the same thing. You're not actually doing anything wrong, this...

This is an untenable situation that makes introducing vim through this plugin to new people impossible. No one takes a plugin that breaks VS Code's `ctrl+p` seriously. If this isn't...

@kossnocorp you're quite right and I apologize for my tactlessness. I only meant to convey, however unskillfully, that this bug is not only an annoyance, and not only breaks the...

> I wouldn't say that it's broken becuase there are simple workarounds discussed in the issues you mentioned I would like to make a strong case that it is in...

No worries, I definitely have a very poor understanding of all the moving pieces here. I don't have any particular opinion on that specific feature, except that I absolutely would...