A C# class library for easily creating a CLI.

I wanted an easy way to execute functions from the command line in a closed environment (so, without using EvaluateExpression etc.).

All expressions are in the format <name> <parameters>.
Commands, like methods, have position arguments and keyword arguments.

Command names must be contain only alphanumeric characters, underscores and hyphens.

• command_name
• CommandName
• 0commandname
• command-name
• commandname0

It is recommended that command names are all lowercase and as short as possible.
E.g. msg is better than send_message and ls is better than list_all_items.

Positional arguments work just as you'd expect.

Arguments are either strings or literals.

• literals contains alphanumeric characters, underscores, hyphens, forward-slashes and periods. They cannot lead with a hyphen.
• strings are enclosed only by double quotes. They can contain any character. \\ will evaluate to \ and \" will evaluate to ".

• command arg1 arg2 arg3
• command "a string argument" arg2 arg3
• command "a string \"something in quotes\"" arg2 "argument number 3"

Tags lead with a hyphen. They can contain alphanumeric characters, hyphens and underscores.
Any arguments that follow a tag are considered to be part of that tag's 'scope' and apply to that tag.
Tags are referenced without the first hyphen -some-tag would be called some-tag and ---some-tag would be called --some-tag.
as a general rule, tags should be spaced with hyphens.
Tags do not need arguments.

• command arg1 -tag arg1 arg2 arg3 tag1 has 3 arguments, arg1, arg2 and arg3.
• command arg1 -tag arg1 "some string argument" -tag2 -tag3 anotherArgument

using Parser.Parse(string plainTextCommand) returns a CommandDetails object that represents a parsed command.

CommandDetails objects contain several readonly attributes.

An array of all the arguments the user has entered. All arguments are strings.
This measns that argument and "argument" are both stored the same.

command arg1 arg2 arg3

{
  Args: [
    "arg1",
    "arg2",
    "arg3"
  ]
}

command "argument one" arg2 "argument number 3"

{
  Args: [
    "argument one",
    "arg2",
    "argument number 3"
  ]
}

Tags are simply stored as a dictionary of arguments.

command -tag1 tag1-arg1 tag1-arg2 -tag2 -tag3 "arguments go here"

{
    Args: [],
    Tags: {
        tag1: [
            "tag1-arg1",
            "tag1-arg2"
        ],
        tag2: [],
        tag3: [
            "arguments go here"
        ]
    }
}

One can easily combine arguments using the operator.
It should be noted that there must be a space either side of the operator.

print "Hello, " World "!"

{
    Args: [
        "Hello, World!"
    ],
    Tags: {}
}

Spreaders are a very useful feature for making certain commands more shorthand.
Spreaders are stored permanently but can be changed at any time.

Let's say we had a command print that prints each positional argument, one after another, delaying by a certain amount of time.

> print "Hello, World!" "Nice to meet you." "My name is Oli." "I am using CommandLineInterface"

might output

Hello, World! | Nice to meet you | My name is Oli. | I am using CommandLineInterface

This output might not be what we normally want - we might have several tags that we use often, for example:

> print "Hello, World!" "Nice to meet you." "My name is Oli." "I am using CommandLineInterface" 
-delay 200 -multi-line -sync -bullet-point "* "

might output

* Hello, World!
* Nice to meet you
* My name is Oli.
* I am using CommandLineInterface

We might want to use these settings a lot.
This is what spreaders are for. Spreaders compact several arguments into a short identifier so that you can be more efficient.

> @PrintSettings -delay 200 -multi-line -sync -bullet-point "* "

To access a spreader:

> print "Hello, World!" "Nice to meet you." "My name is Oli." "I am using CommandLineInterface" @PrintSettings

Another common use-case is to use spreaders in place of long strings.
For example, one can use a spreader to shorten a directory.

> printf Users/Oli/Documents/Coding/Data/groceries.txt 

The above is quite long and would become quite annoying to type all the time, if we want to print things from the Data folder a lot.

> @DataDir Users/Oli/Documents/Coding/Data/
> printf @DataDir   groceries.txt