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
This change will allow commands to define a data type per argument, this
will make the usage more user friendly if commands are getting
registered. You can now choose the data types and the console will
validate the input throwing an error if something went wrong.
Add new method to add commands with strong typed arguments.
Change example to use new method for strong typed arguments.
Fix#43
BREAKING_CHANGE: This will add some breaking changes, if you create a
command instance you cannot use the packedstring array anymore. Instead
create a new "CommandArgument" providing the type as first parameter,
the name as the second and if needed a description of the parameter as
last.
> This will add a new argument but the argument types are defined, this will parse the input data automatically making it easier to use in your method. If a wrong type was provided to any
59
+
> of the arguments an error will be thrown preventing the method execution.
return"[color=red]Command \"%s\" does require (%s) type for argument \"%s\" but provided value was \"%s\"[/color]"% [command_name, expected_type, argument_name, provided_data]
0 commit comments