Syntax lookup: Deprecated decorator

[kevanstannard]

Suggestion for #162

I'm not sure if we have any docs for this one yet so I haven't included any references.

PR should be editable, please feel free edit.

[ryyppy]

Same game here as in the warning attribute... there's I think @@deprecated for the module level as well if i am not mistaken... I guess we can treat module / scope level differently...?

[kevanstannard]

I think @@deprecated for the module level as well if i am not mistaken

Great. It looks like it works as follows:

[1] Use @@deprecated at the file module level.
[2] Use @deprecated for everything else, including modules within files.

Working nicely in VSCode with both @@deprecated and @@deprecated("Some message") syntax.

I guess we can treat module / scope level differently...?

Putting them on different pages in the Syntax Lookup seems sensible to me. I feel that seeing both @deprecated and @@deprecated in the syntax list helps to clarify they two distinct syntaxes.

What do you think?

[ryyppy]

Sounds good! So let's make it clear how each decorator attaches to expressions / modules in separate widget items

[kevanstannard]

Hi @ryyppy, PR updated, what do you think?

[ryyppy]

awesome!

[kevanstannard]

@ryyppy btw, thanks for your suggestions/updates, it's very helpful for me to better understand how some of the concepts should be expressed 🙏