improve completion and onhover in VSCode for decorator and extended model

[RodgeFu]

add following feature

1. support completion when user typing model expression as decorator argument value
2. support completion for extended model
3. support showing decorator model argument prop information when hovering on model expression as decorator argument value

closes #3130, closes #2228, closes #1956

[azure-sdk]

All changed packages have been documented.

• ✅ @typespec/compiler

Show changes

@typespec/compiler - feature ✏️

Support completion for Model with extended properties,> ,> Example,> tsp,> model Device {,> name: string;,> description: string;,> },> ,> model Phone extends Device {,> ┆,> } | [name],> | [description],>

@typespec/compiler - feature ✏️

Support completion for object values and model expression properties.,> ,> Example,> tsp,> model User {,> name: string;,> age: int32;,> address: string;,> },> ,> const user: User = #{name: "Bob", ┆},> | [age],> | [address],>

[azure-sdk]

You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/3280/

Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/3280/

[timotheeguerin]

We have the value world PR that should be merged very soon hopefully. It had object value and array value. Those should be the ones that we autocomplete here instead. Because at this point autocompleting a model like this doesn't make that much sense

[RodgeFu]

We have the value world PR that should be merged very soon hopefully. It had object value and array value. Those should be the ones that we autocomplete here instead. Because at this point autocompleting a model like this doesn't make that much sense

by the "value world", do you mean we will have a new way to define/expose an object value instead of leveraging existing model expression?

[timotheeguerin]

We have the value world PR that should be merged very soon hopefully. It had object value and array value. Those should be the ones that we autocomplete here instead. Because at this point autocompleting a model like this doesn't make that much sense

by the "value world", do you mean we will have a new way to define/expose an object value instead of leveraging existing model expression?

yes exactly, with #{}, this has been merged so you should be able to update that now

[RodgeFu]

yes exactly, with #{}, this has been merged so you should be able to update that now

@timotheeguerin , I have updated the PR accordingly. please help to review again. thanks.

And is there any way that we can get notified in advance for this kind of big change in typespec? That will be helpful for us to collaborate and do planning better. thanks.

[timotheeguerin]

This looks great overall, such a nice addition, there is a few little things missing but thanks for this.