Clarify PROPERTY_HINT_RANGE and PROPERTY_HINT_LINK in class reference#117843
Conversation
Calinou
commented
Mar 25, 2026
- Follow-up to Document creating linked Vector properties in GDScript exports godot-docs#11872.
| </constant> | ||
| <constant name="ERR_PRINTER_ON_FIRE" value="48" enum="Error"> | ||
| Printer on fire error (This is an easter egg, no built-in methods return this error code). | ||
| Printer on fire error (this is an easter egg, no built-in methods return this error code). |
There was a problem hiding this comment.
this line is belong to Error enum, not PropertyHint as mentioned in PR.
so instead, you should untouch this line, and open a separated PR for that.
| Printer on fire error (this is an easter egg, no built-in methods return this error code). | |
| Printer on fire error (This is an easter egg, no built-in methods return this error code). |
There was a problem hiding this comment.
Irrelevant, not out of scope IMO, and not worth making a whole separate PR for
| </constant> | ||
| <constant name="PROPERTY_HINT_NONE" value="0" enum="PropertyHint"> | ||
| The property has no hint for the editor. | ||
| The property has no hint for the editor. However, the hint string is still read, which can be used to specify a suffix for a property that has no range limit (see [constant PROPERTY_HINT_RANGE]'s description). |
There was a problem hiding this comment.
you should fix grammar mistake, and add a reference.
optional PS: add formatting.
| The property has no hint for the editor. However, the hint string is still read, which can be used to specify a suffix for a property that has no range limit (see [constant PROPERTY_HINT_RANGE]'s description). | |
| The property has no hint for the editor. However, when using this one in [annotation @GDScript.export_custom] , the [param]hint_string[/param] mandatory is [i]still[/i] allowed, to specify a suffix for a property that has no range limit (see [constant PROPERTY_HINT_RANGE]'s description). |
There was a problem hiding this comment.
This suggestion is not valid English nor is it correctly formatted
| </constant> | ||
| <constant name="PROPERTY_HINT_RANGE" value="1" enum="PropertyHint"> | ||
| Hints that an [int] 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_less"[/code] to allow manual input going respectively above the max or below the min values. | ||
| Hints that an [int], [float], or packed/typed [Array] property containing [int] or [float] types 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_less"[/code] to allow manual input going respectively above the max or below the min values. |
There was a problem hiding this comment.
you should fix grammar mistake.
| Hints that an [int], [float], or packed/typed [Array] property containing [int] or [float] types 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_less"[/code] to allow manual input going respectively above the max or below the min values. | |
| Hints that an [int], [float], or packed/typed [Array] property (whose types are [int] or [float] ) 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_less"[/code] to allow manual input going respectively above the max or below the min values. |
There was a problem hiding this comment.
The original isn't incorrect I'd say, please explain (also your suggestion is incorrectly formatted), your suggestion is also incorrect grammatically, unlike the original
AThousandShips
left a comment
There was a problem hiding this comment.
LGTM, good additions and fixes
|
Thanks! |