Missing space after colon with auto-complete

[adamaltman]

What happened?

I was writing properties.

type: object
properties:
  myPropName:
    type:

When I selected type I ended up with type: without a trailing space and yaml requires a space after a colon.

This is medium priority because of the frequency (this will happen to me about 100 times today).

This same issue happens with other selections too such as default: etc...

What should have happened instead?

The extension should have had a space. Also, when the space is there, there is a menu to autocomplete the type (e.g. string).

Minimal reproducible OpenAPI snippet

See above.

Screenshots

Short video snippet:

missing-space-vs-code.mp4

Additional context

v0.2.9

[SmoliyY]

@adamaltman After each auto-complete we also can trigger next suggestion for value, not only for type. I am not sure if it's will be annoying for user but we can try with that. What do you think?

[adamaltman]

I think that would be cool @SmoliyY (I didn't see this notification -- sorry, I get a lot)