-
-
Notifications
You must be signed in to change notification settings - Fork 23.6k
Description
This is a follow-up to the mega tracker #16863 which we've used for the past 3 years to keep a list of things we'd like to rename in the API for Godot 4.0.
Many of these renames have been done, some are still pending with open PRs, others might actually not be wanted, as we didn't do thorough discussion of all proposals on that issue.
Now that we're getting closer to the 4.0 release, it's time to give this a second look, and start anew from the current API.
Are there more classes, methods, properties, or signals, which have an awkward name and could be improved before we freeze the API to preserve compatibility?
Here's my workflow proposal for this tracker:
- Add your suggestions as comments below. Include links to relevant proposals or issues/comments if they exist (but you don't necessarily need to open a proposal for it, unless it's a very substantial change to the API).
- Upvote the proposals you support, downvotes the ones you disagree with. Don't take downvotes personally, we need to assess the general feeling of the community for a given proposal to see if it makes sense to rename, beyond core maintainers' own intuition.
- If you're motivated, you can also salvage unresolved suggestions from [TRACKER] Methods, properties and signals to consider for renaming in next planned compatibility breakage #16863 so they are considered again here (beware, there are 500 comments...).
- Suggestions (not approved yet, so don't open PRs for them) will be listed by repo maintainers in the second comment of this issue.
- Avoid lengthy discussions of suggestions in this tracker, as it makes it hard to keep track of things. Prefer discussion on the Contributor Chat, and if needed, open dedicated proposals for non-consensual suggestions that require more debate.
- After review, approved suggestions will be moved to the task list below in this first comment, so they can be implemented by contributors and merged.
Important: This tracker is only for API renames. I.e. changing a name to another name, not changing behavior, adding/removing logic, etc. Anything that changes the behavior of the engine should be discussed in a proposal on https://github.com/godotengine/godot-proposals.
For this tracker, let's also exclude suggestions for changes in the Project Settings and Editor Settings. Those should probably have their own trackers, as the settings do need a cleanup for 4.0.
Approved renames
None yet.