You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we parse the parameter column documentation as a string with no implicit type definition. We thus cannot easily infer the parameter type for things like the LuaLS definition parser, or type linking like we have with arguments.
Since it is currently parsed as a string, we would have to perform a special operation on this field to extract any prefixed type information, which is not ideal. Maybe it would make more sense to implement a separate tag like < and > for the documentation parser, so it knows when to extract type information?
Leaving link to one of the documentation table values below.
Currently we parse the parameter column documentation as a string with no implicit type definition. We thus cannot easily infer the parameter type for things like the LuaLS definition parser, or type linking like we have with arguments.
Since it is currently parsed as a string, we would have to perform a special operation on this field to extract any prefixed type information, which is not ideal. Maybe it would make more sense to implement a separate tag like < and > for the documentation parser, so it knows when to extract type information?
Leaving link to one of the documentation table values below.
Eluna/methods/TrinityCore/GlobalMethods.h
Line 672 in bf579dd
Proposed format:
* @values [1, ON_CHARACTER_CREATE, "WORLD", <event: Number, player: Player>, ""]
The text was updated successfully, but these errors were encountered: