GDQuest/GDScript-formatter

Description The rule private-access is triggered when accessing a private instance member from a static context within the same class. See the example below. The rule message is "... should not be accessed from outside its class" which let me think this is not intentional and is a bug. Reproduce class_name Foo var _data: int func _method() -> void: pass static func do(foo: Foo) -> void: foo._data = 0 foo._method() Expected behaviour No linter rule triggered. Observed behaviour The above example triggers : [private-access] Private variable '_data' should not be accessed from outside its class [private-access] Private method '_method' should not be accessed from outside its class But this is not an access from outside the class...

Description Using GDScript formatter 0.18.2 with Godot 4.6 on Windows On linting a file, problematic lines are colored in red or yellow to indicate a linter error or warning. These colors disappear within 1-2 seconds of editing the script in Godot script editor (even without saving the file). Reproduce Write a script with a linter issue : func _init() -> void: print("hello") pass # <- this produces a linter warning (unnecessary-pass) Lint it (Ctrl+S or Format > Lint Current Script). The pass line is now colored in yellow. Edit it (you can just add a new line, or edit the comment). Expected behaviour The pass line coloration do not change. Observed behaviour The pass line coloration disappear after 1-2 seconds. Additional informations This behaviour can be indirectly triggered by saving the script, because saving the script can trigger the formatting and edit the script. Also: Godot seems to redraw the script editor if the script is edited, then left unedited for 1-2 seconds