Some listable types should not enforce uniqueness

[FableRBX]

Array type arguments (ex: "strings" type) are not being parsed into arrays in sequential order.
For example, the following command definition has its third argument of type "strings"

return {
    Name = "dev",
    Description = "Runs an internal developer command.",
    Group = "Admin",
    Args = {
        {
            Type = "string",
            Name = "Command",
            Description = "The internal command to run.",
        },
        {
            Type = "player",
            Name = "target",
            Description = "The target player to run command for.",
        },
        {
            Type = "strings";
            Name = "dataArgs";
            Description = "List of data arguments.";
        },
    }

When entering a series of strings on the command line, they are provided in an argument table out of order.

[FableRBX]

Tested using "numbers" instead of "strings" and the order appears to be maintained for numbers but not strings 🤔

[evaera]

This behavior is intended, because lists are more like sets in that they can only contain a value once at most. I can see why this would be undesirable at times, so it would be nice to have this uniqueness be optional.

The reason Cmdr does this is for in the case of commands that take players, it would probably be unexpected if the resultant array contained a player more than once. However for strings, the natural intuition is probably the opposite.

[FableRBX]

Ok, closing issue in that case!

[evaera]

I'd like to keep it open as this is still a problem that needs to be addressed. I think maybe the uniqueness should only be enforced for certain types.