This is absolutely fantastic and something I have been want for ages. I've looked into it but the learning curve was just a bit much for me. Thank you so much for doing this and I will be actively using this and providing feedback where I can. I can already provide some, though I realize that some of these things might not be very high on the priority list.
Allow for changing the syntax highlight coloring (this can be done in user settings but isn't quite as performant as if it's done by the lexer).
As part of this, it would be nice if there was some more distinction between the token identifiers. Variable names in declarations aren't getting noted as variables. Not sure if that's a limitation or what
Small thing, but the settings being in the settings menu. I don't know where geckrc.json files are to modify them, unless it can be added to the user settings file as is. Just a QOL thing.
Not sure if I'm doing it wrong, but I'm not getting definition/reference data for my functions as they are in different scripts. Ex. Trying to get references from the name declaration of a script returns nothing, but I can get references for a UDF if selecting it in the body of a code block. Expected behavior is that Definition would take me to or open the file of the same name, and References on the name of the script in its definition file would show me all places it's used in the project.
Would be really cool to see an option to open a geckwiki page for the selected function.
Thanks a lot for your feedback, I'm glad you liked my project! The new version should address all the points you raised:
I'm not sure it can be done on the server level. The server can classify the tokens into a limited set of categories, but the colors are handled purely by the client. That being said, I did add some more token types, and variables in declarations should be fixed
Added settings to VS Code. The geckrc.json file can be anywhere with the script files, my bad, should've made that more clear
Should be fixed
There was already a link when hovering over the function, but now there is also a link in the completion documentation, and a code action to go to the GECK wiki
Once again, the feedback is highly appreciated! Feel free to post about any other concerns or requests you have!
9 comments
Super Endorsed
Once again, the feedback is highly appreciated! Feel free to post about any other concerns or requests you have!