Wrapper function for onCreate appearing unexpectedly in room's On Create IDE

[oaklandgit]

Describe the bug
See this screenshot. Notice how the onCreate function is appearing in the IDE. Also notice the repeated line number 1.
The problem fixed itself after restarting ctjs.

To Reproduce
Unfortunately, I'm not sure how to reproduce this.

System information report
Ct.js v1.7.0 😽 (packaged)

NW.JS v0.51.2
Chromium v88.0.4324.182
Node.js v15.8.0
Pixi.js v5.1.2

WebGL available
WebGL vendor Intel Inc.
WebGL renderer Intel(R) Iris(TM) Plus Graphics OpenGL Engine
OS darwin x64 // Darwin 20.3.0

[oaklandgit]

Can happen with any tab. (e.g. On Draw).

[CosmoMyzrailGorynych]

This is the result of my workarounds for monaco's issue microsoft/monaco-editor#45

The problem fixed itself after restarting ctjs.

Can be fixed by closing and reopening type editor / room events editor.

Unfortunately, I'm not sure how to reproduce this.

One of the ways to get a variation of this bug:

1. Open a code editor of a type or a room
2. Write anything on the first line
3. Alt+Up arrow
4. The line disappears
5. Reopen the asset editor
6. You can now see a wrapping function. (Another one gets created and is invisible so removing the one inside your code will fix the issue)

[stale]

Hey there 👋 I marked this issue as stale as it hadn't brought much attention for quite a while.
I do understand that stale issues are still issues, yet here stale issues receive the least attention from maintainers so they can focus on more relevant tasks. You can help with this issue by checking whether it affects latest versions of ct.js and writing about it if it does, providing an example project and steps to reproduce. Or maybe you can close it with a PR!
Note that some platform-dependent issues can't be resolved by developers due to the absense of such devices :c We will need help from you for such tasks.
If this issue won't get attention in three months, it will be closed.

[stale]

This issue is now closed! Please create a new one with a proper template if this issue still affects ct.js.