Skip to content

[TRACKER] Methods, properties and signals to consider for renaming in next planned compatibility breakage #16863

@akien-mga

Description

@akien-mga

This issue is meant to keep track of awkwardly named or deprecated methods, properties and signals that we would like to rename next time we have the opportunity.

This can't be done lightly as it breaks compatibility for users using their old names, so any such change has to be done:

  • either after following a deprecation procedure: marked as deprecated - using it shows a warning - for at least one full minor release cycle (e.g. 3.1.x), then removed in a future minor or major version bump,
  • or within a major compatibility breaking release (such as 3.0 was to 2.1; but such situations won't happen often - if ever again - so the deprecation workflow should be preferred).

To properly deprecate methods, properties and signals, we need #4397 implemented.

A 🎉 reaction added by @akien-mga or @Calinou means the suggestion in the comment was incorporated into this post.


Classes

- [ ] OS* could be renamed to Platform* #16863 (comment) (See #47789 (comment))
- [ ] Label: Consider renaming to TextLabel #16863 (comment) (see #40124 (comment))

Methods

Properties

Signals

Enums

Constants

  • Global Scope: PROPERTY_USAGE_STORE_IF_NONZERO and PROPERTY_USAGE_STORE_IF_NONONE should be fully dropped, also from GDNative Remove obsolete enums #37693

Theme items

Objects

Shading language

  • WORLD_MATRIX is actually a model-view matrix and should be renamed. @reduz suggests to replace it (and CAMERA_MATRIX, which is a view matrix) by actual view and model matrices, e.g. CANVAS_MATRIX and ITEM_MATRIX.

Project settings

File formats

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions