godotengine / godotengine/godot

[TRACKER] GDScript `class_name`

Open
#99,766 0 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

topic:gdscript tracker
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

Issues
  • godotengine/godot#30048
  • godotengine/godot#48311
  • godotengine/godot#56628
  • godotengine/godot#81222
  • godotengine/godot#82479
  • godotengine/godot#83395
  • godotengine/godot#83542
  • godotengine/godot#83561
  • godotengine/godot#90240
  • godotengine/godot#94378
  • godotengine/godot#98985
Proposals
Some issues brought up by class_name
  • Addon authors avoid them because of possible naming conflicts.
  • In some cases, scripts with preload() via transitive dependencies can load a lot of the project resources.
  • Global classes clutters the node/resource creation dialog.
    • godotengine/godot#91020
    • godotengine/godot#95806
  • There are no namespaces.

Many thanks to @dalexeev for the list.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the unchecked issues and proposal 1047 listed in this tracker, along with the checked items for context. The issue does not define a specific change or completion criteria; progress would require deciding which class_name problems and proposal work to address.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.