Fix return keyword as it appears in code completion

[aparajit-pratap]

Purpose

Fix return keyword as it appears in code completion.

Before:

After:

Declarations

Check these if you believe they are true

• The code base is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• [] Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning, and are documented in the API Changes document.

Reviewers

@mjkkirschner
@QilongTang

[QilongTang]

This is impressive, how did you find the issue? Is there a github issue on this or from your own testing?

[aparajit-pratap]

This is impressive, how did you find the issue? Is there a github issue on this or from your own testing?

It's been around for ages, I found it very annoying.

[QilongTang]

@aparajit-pratap LGTM off course. But was curious why it was "return_reserved"

[aparajit-pratap]

@QilongTang the return_reserved was named that way as return is a reserved keyword in DesignScript and before autocomplete in code block nodes we weren't exposing it to the user so it didn't matter. I don't think it was updated after the introduction of autocomplete but I could be wrong.