Some Feather-style types are treated as incompatible with their GMEdit counterparts

[thennothinghappened]

GMEdit currently uses its own type naming scheme which runs in contrast with Feather's own naming.

The main issue with this is that both can use the same JSDoc formatting for function arguments, but switching between the IDE and GMEdit will cause both to complain about eachother's types.

Some examples:

Feather	GMEdit
Real	number or int
Asset.GMObject<T>	object or T (as asset ID)
Id.Instance<T>	object or T (as instance)
Id.Buffer	buffer
Id.VertexBuffer	vertex_buffer
Id.Surface	surface
Asset.GMSprite<T>	sprite
Constant.Colour	int
...	...

Solutions?

The two solutions I can think of is either adopting Feather's types, or making them aliases in some sense to GMEdit's equivalent types. The latter of these makes more sense to me as it doesn't make existing GMEdit types incorrect.

[YellowAfterlife]

I do have aliases for most of them, you can see these as fe_name in api directory and add the missing ones https://github.com/YellowAfterlife/GMEdit/blob/master/bin/resources/app/api/shared/types.gml

[thennothinghappened]

Interesting, I can't seem to get those to work. I tried id.dslist for example and the variable did not show any type on hover, whereas ds_list worked.

[YellowAfterlife]

It's done with jsdoc, like so

[thennothinghappened]

Here's an example of the sort of issue I'm referring to (only took me 2 years to write down the repro steps!):

/// @param _pattern Pattern that was instantiated.
/// @param {Real} _spawnedAtTime When, on the game clock, this pattern was instantiated.
function PatternInstance(_pattern, _spawnedAtTime) constructor {
	pattern = _pattern;
	spawnedAtTime = _spawnedAtTime;
}

activePatternInstances = []; /// @is {Array<Struct.PatternInstance>}
activePatternInstances[0] = new PatternInstance(0, 0);

---

function SomeStruct() constructor {}

/// @param {Struct.SomeStruct} someStruct
function someFunction(someStruct) {
	
}

someFunction(new SomeStruct());