godotengine/godot-vscode-plugin
1
0
Fork 0
mirror of https://github.com/godotengine/godot-vscode-plugin.git synced 2026-02-26 00:53:27 +03:00
Code Issues Packages Projects Releases Wiki Activity
Files
3f7a944e967856b5d0dc65045f1696c00234d006
godot-vscode-plugin/syntaxes
History
David Kincaid 3f7a944e96 More Highlighting and Formatting Improvements (#783) 
* Fix **= operator being formatted incorrectly

* Fix variables in get_node()-style function calls not being highlighted

* Move super from builtin_classes to keywords

* Fix uppercase builtin classes being highlighted as constants

* Fix setter and getter highlighting/formatting

* Fix variable as default parameter not highlighted in function declaration
2025-02-22 12:51:44 -05:00
..
examples
Fix bare nodepaths referencing absolute/root paths (#712)
2024-09-15 16:04:31 -04:00
.prettierrc.json
Fix keywords being incorrectly highlighted as function calls (#353)
2022-04-28 01:16:44 +02:00
GDResource.tmLanguage.json
Various QoL Improvements (#529)
2023-12-06 06:53:10 -08:00
GDScript.tmLanguage.json
More Highlighting and Formatting Improvements (#783)
2025-02-22 12:51:44 -05:00
GDShader.tmLanguage.json
Various QoL Improvements (#529)
2023-12-06 06:53:10 -08:00
README.md
Change $ node path shorthand regex to match only valid paths (#276)
2021-06-15 18:39:29 +02:00

README.md

Helpful resources

You can find the regex syntax that VSCode uses here.

Creating and debugging regex

When creating regexes it is sometimes useful to test against a data set.

Regex101 allows for pretty good match testing. Unfortunately, it does not support the regex (Ruby) version that TextMate uses.

ExtendsClass's regex engine does support the Ruby variant, but the match testing experience is not as good. However, it automatically generates an FSM for your regex, which is very useful when debugging.