Fix GDScript error when using an inherited const as annotation#57510
Fix GDScript error when using an inherited const as annotation#57510trollodel wants to merge 1 commit intogodotengine:masterfrom
Conversation
2105c4e to
d712fe9
Compare
|
I believe this doesn't cover enough cases, as it's not checking the inheritance tree of the inner class itself (only for the outermost class). So the proper way would be to check the inherited constants of the current class, then go the outer one and do the same, then the outer one from that and so on. It's complicated but it should solve all cases. If you want to do it I can help, otherwise I'll tackle it later. |
Yeah, I suspected that (see the note in the OP).
I can work on it, but not in the near future. The idea I had is to have this completed and then work on the other cases in another PR, but I understand why you may want to fix all the cases here. |
3d2392f to
834cc8e
Compare
834cc8e to
64b70ac
Compare
64b70ac to
818d33c
Compare
818d33c to
30e4394
Compare
|
Superseded by #69587. |
Fix a GDScript analyzer error when using as an annotation a class declared as
constwhich is declared in the parent script (or in a relative one). Regardless the fact is not ideal, declaring again the const class in the child script raises an error because the const is already declared, preventing to workaround the issue.Example:
This PR includes an integration test for this issue.