[API] Property type hint is exported as property type in api if using a TypedArray of Resources

[piiertho]

Godot version

4.0.dev (d0398f6)

System information

Windows 10

Issue description

Api export hint string as type when using a TypedArray.
Here is an example for SystemFont::fallbacks:

				{
					"type": "typedarray::24/17:Font",
					"name": "fallbacks",
					"setter": "set_fallbacks",
					"getter": "get_fallbacks"
				}

This issue was already present in former api: godotengine/godot-headers#67.

Steps to reproduce

N/A

Minimal reproduction project

N/A

[akien-mga]

That's intentional, no? To handle typed arrays you need information on their type, which is provided here.

See #65817 which implemented it, and further discussion in #64249.

[CedNaru]

We only need the information about the subtype for the Array, the rest of the hint string doesn't bring new information.
In the example, typedarray::Font is plenty enough for creation of bindings (which should result naturally into something close to Array<Font> in a typed language with generics).

From what I understand, the original HintString used for the Font fallback is there for the inspector, so it doesn't let you add any kind of Object in the array but only the Font type.

I don't think that information is necessary in the api.json, but if somehow it was, we should have a more consistent behaviour then. As it is right now, we get our regular typedarray::SubType in almost all cases of Typed arrays and then we have this corner case like this with a different format typedarray::HintString.

[CedNaru]

Also should be noted that this behavior doesn't happen when it's written as the type of method argument:

Only when it's a property it behaves like this:

Of course we have other occurences of that, each time it's a typedArray property with a ressource as Subtype:

Everytime it's the same hintstring 24/17/Subtype, the presence of the same prefix means it doesn't provide new informations.