Support both command id orders
Currently BusyList only supports the <id> command pattern, but many people have suggested command <id>. We should support both ways.
Describe how this new feature adds value to the application
It allows the user to use whatever command pattern they feel is more intuitive.
Describe suggested implementation
For each command, support both patterns in the CommandGrammar class.
This is pretty much the easiest change to the parsing grammar possible, so I think it would be an excellent issue for someone who wants to get more familiar with parsing and Sprache.
Additional context
Support both command id orders
Currently BusyList only supports the
<id> commandpattern, but many people have suggestedcommand <id>. We should support both ways.Describe how this new feature adds value to the application
It allows the user to use whatever command pattern they feel is more intuitive.
Describe suggested implementation
For each command, support both patterns in the
CommandGrammarclass.This is pretty much the easiest change to the parsing grammar possible, so I think it would be an excellent issue for someone who wants to get more familiar with parsing and Sprache.
Additional context