You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem or limitation you are having in your project
Since most example code and snippets available are made for Godot 3 or earlier, figuring out how to do something new is now to me often a process of first finding a Godot 3 example code on how to do it, see if that still runs. If it doesn't check what API changes might be needed to get it to run. More often than not it's just simple renaming of properties (like get_font() to theme_get_font() etc). It's doable, but it could be nice if this was smoother.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Add some hints in the editor or debugger on rows where there are errors to show suggested changes based on Godot 3->4 API changes, to help the user quickly convert and reuse old code snippets without needing to do another round of research in the docs or on the web.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Since there's now a project import tool #387 implemented that I assume does code analysis and translation for exactly these same cases my proposal would be to reuse this to provide hints for individual rows in error messages. Either in the debugger or the editor errors.
For example, if there's an error like calling a method that doesn't exist or trying to access a property that doesn't exist, use the converter tool on the line of code to see if that would result in any changes. If it does, show this information as some sort of hint for the line with the issue, or maybe even a suggested conversion the user can apply with a single click.
If this enhancement will not be used often, can it be worked around with a few lines of script?
no
Is there a reason why this should be core and not an add-on in the asset library?
It would be an integrated feature of the debugger/compiler/editor but maybe it could be made an add-on as well.
The text was updated successfully, but these errors were encountered:
Describe the project you are working on
My first Godot 4 project
Describe the problem or limitation you are having in your project
Since most example code and snippets available are made for Godot 3 or earlier, figuring out how to do something new is now to me often a process of first finding a Godot 3 example code on how to do it, see if that still runs. If it doesn't check what API changes might be needed to get it to run. More often than not it's just simple renaming of properties (like
get_font()
totheme_get_font()
etc). It's doable, but it could be nice if this was smoother.Describe the feature / enhancement and how it helps to overcome the problem or limitation
Add some hints in the editor or debugger on rows where there are errors to show suggested changes based on Godot 3->4 API changes, to help the user quickly convert and reuse old code snippets without needing to do another round of research in the docs or on the web.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Since there's now a project import tool #387 implemented that I assume does code analysis and translation for exactly these same cases my proposal would be to reuse this to provide hints for individual rows in error messages. Either in the debugger or the editor errors.
For example, if there's an error like calling a method that doesn't exist or trying to access a property that doesn't exist, use the converter tool on the line of code to see if that would result in any changes. If it does, show this information as some sort of hint for the line with the issue, or maybe even a suggested conversion the user can apply with a single click.
If this enhancement will not be used often, can it be worked around with a few lines of script?
no
Is there a reason why this should be core and not an add-on in the asset library?
It would be an integrated feature of the debugger/compiler/editor but maybe it could be made an add-on as well.
The text was updated successfully, but these errors were encountered: