PropertyHints listed in VisualScriptEditorVariableEdit are out of sync

[kleonc]

Godot version

e5c6c77

System information

N/A

Issue description

Note sure what exactly is it used for, didn't dig into it. Noticed it because that's the only place where "ExpRange" still occurs:

godot/modules/visual_script/visual_script_editor.cpp

Lines 324 to 325 in e5c6c77

// Update this when PropertyHint changes.

p_list->push_back(PropertyInfo(Variant::INT, "hint", PROPERTY_HINT_ENUM, "None,Range,ExpRange,Enum,ExpEasing,Length,SpriteFrame,KeyAccel,Flags,Layers2dRender,Layers2dPhysics,Layer3dRender,Layer3dPhysics,File,Dir,GlobalFile,GlobalDir,ResourceType,MultilineText,PlaceholderText,ColorNoAlpha,ImageCompressLossy,ImageCompressLossLess,ObjectId,String,NodePathToEditedNode,MethodOfVariantType,MethodOfBaseType,MethodOfInstance,MethodOfScript,PropertyOfVariantType,PropertyOfBaseType,PropertyOfInstance,PropertyOfScript,ObjectTooBig,NodePathValidTypes"));

godot/doc/classes/@GlobalScope.xml

Lines 2239 to 2356 in e5c6c77

	<constant name="PROPERTY_HINT_NONE" value="0" enum="PropertyHint">
	No hint for the edited property.
	</constant>
	<constant name="PROPERTY_HINT_RANGE" value="1" enum="PropertyHint">
	Hints that an integer or float property should be within a range specified via the hint string [code]"min,max"[/code] or [code]"min,max,step"[/code]. The hint string can optionally include [code]"or_greater"[/code] and/or [code]"or_lesser"[/code] to allow manual input going respectively above the max or below the min values. Example: [code]"-360,360,1,or_greater,or_lesser"[/code].
	Additionally, other keywords can be included: "exp" for exponential range editing, "radians" for editing radian angles in degrees, "degrees" to hint at an angle and "noslider" to hide the slider.
	</constant>
	<constant name="PROPERTY_HINT_ENUM" value="2" enum="PropertyHint">
	Hints that an integer, float or string property is an enumerated value to pick in a list specified via a hint string such as [code]"Hello,Something,Else"[/code].
	</constant>
	<constant name="PROPERTY_HINT_ENUM_SUGGESTION" value="3" enum="PropertyHint">
	Hints that a string property is can be an enumerated value to pick in a list specified via a hint string such as [code]"Hello,Something,Else"[/code].
	Unlike [constant PROPERTY_HINT_ENUM] a property with this hint still accepts arbitrary values and can be empty. The list of values serves to suggest possible values.
	</constant>
	<constant name="PROPERTY_HINT_EXP_EASING" value="4" enum="PropertyHint">
	Hints that a float property should be edited via an exponential easing function. The hint string can include [code]"attenuation"[/code] to flip the curve horizontally and/or [code]"inout"[/code] to also include in/out easing.
	</constant>
	<constant name="PROPERTY_HINT_LENGTH" value="5" enum="PropertyHint">
	Deprecated hint, unused.
	</constant>
	<constant name="PROPERTY_HINT_KEY_ACCEL" value="6" enum="PropertyHint">
	Deprecated hint, unused.
	</constant>
	<constant name="PROPERTY_HINT_FLAGS" value="7" enum="PropertyHint">
	Hints that an integer property is a bitmask with named bit flags. For example, to allow toggling bits 0, 1, 2 and 4, the hint could be something like [code]"Bit0,Bit1,Bit2,,Bit4"[/code].
	</constant>
	<constant name="PROPERTY_HINT_LAYERS_2D_RENDER" value="8" enum="PropertyHint">
	Hints that an integer property is a bitmask using the optionally named 2D render layers.
	</constant>
	<constant name="PROPERTY_HINT_LAYERS_2D_PHYSICS" value="9" enum="PropertyHint">
	Hints that an integer property is a bitmask using the optionally named 2D physics layers.
	</constant>
	<constant name="PROPERTY_HINT_LAYERS_2D_NAVIGATION" value="10" enum="PropertyHint">
	Hints that an integer property is a bitmask using the optionally named 2D navigation layers.
	</constant>
	<constant name="PROPERTY_HINT_LAYERS_3D_RENDER" value="11" enum="PropertyHint">
	Hints that an integer property is a bitmask using the optionally named 3D render layers.
	</constant>
	<constant name="PROPERTY_HINT_LAYERS_3D_PHYSICS" value="12" enum="PropertyHint">
	Hints that an integer property is a bitmask using the optionally named 3D physics layers.
	</constant>
	<constant name="PROPERTY_HINT_LAYERS_3D_NAVIGATION" value="13" enum="PropertyHint">
	Hints that an integer property is a bitmask using the optionally named 2D navigation layers.
	</constant>
	<constant name="PROPERTY_HINT_FILE" value="14" enum="PropertyHint">
	Hints that a string property is a path to a file. Editing it will show a file dialog for picking the path. The hint string can be a set of filters with wildcards like [code]"*.png,*.jpg"[/code].
	</constant>
	<constant name="PROPERTY_HINT_DIR" value="15" enum="PropertyHint">
	Hints that a string property is a path to a directory. Editing it will show a file dialog for picking the path.
	</constant>
	<constant name="PROPERTY_HINT_GLOBAL_FILE" value="16" enum="PropertyHint">
	Hints that a string property is an absolute path to a file outside the project folder. Editing it will show a file dialog for picking the path. The hint string can be a set of filters with wildcards like [code]"*.png,*.jpg"[/code].
	</constant>
	<constant name="PROPERTY_HINT_GLOBAL_DIR" value="17" enum="PropertyHint">
	Hints that a string property is an absolute path to a directory outside the project folder. Editing it will show a file dialog for picking the path.
	</constant>
	<constant name="PROPERTY_HINT_RESOURCE_TYPE" value="18" enum="PropertyHint">
	Hints that a property is an instance of a [Resource]-derived type, optionally specified via the hint string (e.g. [code]"Texture2D"[/code]). Editing it will show a popup menu of valid resource types to instantiate.
	</constant>
	<constant name="PROPERTY_HINT_MULTILINE_TEXT" value="19" enum="PropertyHint">
	Hints that a string property is text with line breaks. Editing it will show a text input field where line breaks can be typed.
	</constant>
	<constant name="PROPERTY_HINT_PLACEHOLDER_TEXT" value="20" enum="PropertyHint">
	Hints that a string property should have a placeholder text visible on its input field, whenever the property is empty. The hint string is the placeholder text to use.
	</constant>
	<constant name="PROPERTY_HINT_COLOR_NO_ALPHA" value="21" enum="PropertyHint">
	Hints that a color property should be edited without changing its alpha component, i.e. only R, G and B channels are edited.
	</constant>
	<constant name="PROPERTY_HINT_IMAGE_COMPRESS_LOSSY" value="22" enum="PropertyHint">
	Hints that an image is compressed using lossy compression.
	</constant>
	<constant name="PROPERTY_HINT_IMAGE_COMPRESS_LOSSLESS" value="23" enum="PropertyHint">
	Hints that an image is compressed using lossless compression.
	</constant>
	<constant name="PROPERTY_HINT_OBJECT_ID" value="24" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_TYPE_STRING" value="25" enum="PropertyHint">
	Hint that a property represents a particular type. If a property is [constant TYPE_STRING], allows to set a type from the create dialog. If you need to create an [Array] to contain elements of a specific type, the [code]hint_string[/code] must encode nested types using [code]":"[/code] and [code]"/"[/code] for specifying [Resource] types. For instance:
	[codeblock]
	hint_string = "%s:" % [TYPE_INT] # Array of inteters.
	hint_string = "%s:%s:" % [TYPE_ARRAY, TYPE_REAL] # Two-dimensional array of floats.
	hint_string = "%s/%s:Resource" % [TYPE_OBJECT, TYPE_OBJECT] # Array of resources.
	hint_string = "%s:%s/%s:Resource" % [TYPE_ARRAY, TYPE_OBJECT, TYPE_OBJECT] # Two-dimensional array of resources.
	[/codeblock]
	[b]Note:[/b] the final colon is required to specify for properly detecting built-in types.
	</constant>
	<constant name="PROPERTY_HINT_NODE_PATH_TO_EDITED_NODE" value="26" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_METHOD_OF_VARIANT_TYPE" value="27" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_METHOD_OF_BASE_TYPE" value="28" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_METHOD_OF_INSTANCE" value="29" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_METHOD_OF_SCRIPT" value="30" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_PROPERTY_OF_VARIANT_TYPE" value="31" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_PROPERTY_OF_BASE_TYPE" value="32" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_PROPERTY_OF_INSTANCE" value="33" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_PROPERTY_OF_SCRIPT" value="34" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_OBJECT_TOO_BIG" value="35" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_NODE_PATH_VALID_TYPES" value="36" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_SAVE_FILE" value="37" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_INT_IS_OBJECTID" value="38" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_INT_IS_POINTER" value="40" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_ARRAY_TYPE" value="39" enum="PropertyHint">
	</constant>
	<constant name="PROPERTY_HINT_MAX" value="41" enum="PropertyHint">
	</constant>

Steps to reproduce

N/A

Minimal reproduction project

N/A

[Xrayez]

I submitted a PR for this in the past: #43211. I closed it because I haven't received any feedback regarding the issue, and out of sync wasn't an issue back then. But the current way of having to hardcode values is definitely not future-proof and error-prone.

[KoBeWi]

VisualScript was removed in Godot 4.0, so closing.