BowlerHatLLC / vscode-as3mxml

ActionScript & MXML language extension for Visual Studio Code. Develop apps for Adobe AIR, Adobe Flash Player, or Apache Royale.
https://as3mxml.com/
Apache License 2.0
256 stars 39 forks source link

Code completion showing snippets instead of symbols #696

Closed ylazy closed 1 year ago

ylazy commented 1 year ago

https://github.com/BowlerHatLLC/vscode-as3mxml/assets/6010183/f38868b1-c371-48e3-99dc-8150a1e033d2

Restarting the extension did NOT fix the problem. The extension host output:

restart-as3mxml.txt

Restarting VSCode did fix the problem, but after coding for a while, the issue happened again.

restart-vscode.txt

I'm using the latest build.

joshtynjala commented 1 year ago

The "Extension host" output rarely provides useful output related to completion. Is there any output for the AS3/MXML language server instead?

ylazy commented 1 year ago

This is the ActionScript & MXML Language Server output when the issue happened:

The output displayed when I type t then this. in the class Ticker. as3-output.txt

https://github.com/BowlerHatLLC/vscode-as3mxml/assets/6010183/622bad19-2187-4c2d-bf54-8642f50455e0

ylazy commented 1 year ago

And this is the output after I reloaded the VSCode and try again: success-output.txt

https://github.com/BowlerHatLLC/vscode-as3mxml/assets/6010183/7b38aa18-00df-4077-87a0-fa0f5d9ef898

joshtynjala commented 1 year ago

The output displayed when I type t then this. in the class Ticker.

That's just the output you see when you use the actionscript.trace.server setting. But you're right. No errors. Interestingly, though, there are no completion requests at all in this log. That seems strange.

I have no idea what's wrong, and I cannot reproduce yet. I made a number of commits last week to fix the duplicate function issue, and to add sorting to completion items based on your suggestions. You might try rolling back some of those commits to see if any caused this issue. That might give us some clues.

ylazy commented 1 year ago

It's strange. I didn't do anything but the issue didn't happen anymore. Maybe it's related to caching. I'll need more time to test and I'll update this when I can find a way to reproduce the problem. Thanks!