API renames for Goost 2.0 #176
Replies: 4 comments 2 replies
-
|
The following renames stem from eliminating redundancy with using
This class was first renamed from
Since |
Beta Was this translation helpful? Give feedback.
-
|
If godotengine/godot-proposals#3948 is implemented in Goost, do you think it would make sense to rename:
Having both Update: renamed in #181. |
Beta Was this translation helpful? Give feedback.
-
|
I propose the following Random is very common word. It can potentially cause conflicts with custom classes or addons. I only encountered this issue in 2 situations: my game used to use Random custom class and and an addon though I forget which one right now. |
Beta Was this translation helpful? Give feedback.
-
|
How about renaming See also #174 (reply in thread) Note that there's |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Lets discuss what kind of classes, methods, properties etc. that would benefit from renaming in Goost
Note: this list should not be confused with Godot's API renaming, if you have a suggestion specifically for Godot API, feel free to do so at godotengine/godot#54161.
Classes
VariantMap→Map2DRenameVariantMapandVariantResourceclasses #182VariantResource→DataContainerRenameVariantMapandVariantResourceclasses #182Beta Was this translation helpful? Give feedback.
All reactions