Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleaner handling of commands and command args #16

Open
reakain opened this issue Jan 15, 2020 · 1 comment
Open

Cleaner handling of commands and command args #16

reakain opened this issue Jan 15, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@reakain
Copy link
Member

reakain commented Jan 15, 2020

Command names are currently in their own static list, but the args for each command are currently hardcoded in place. Add some sort of method for tracking/maintaining those arg names and methods?

@reakain reakain added the enhancement New feature or request label Jan 15, 2020
@BlinkTheThings
Copy link
Member

I also think we should have a better separation between different types of commands.
There are three types of commands as of now:

  1. Console commands
  2. Control commands
  3. Message commands

Console commands are not sent over network and configure things on the local machine.
Control commands are sent over the network and are related to user presence, channels, etc.
Message commands are text messages that are sent to groups or individuals.

I want to change the network protocol to support a more well-defined format for control and message commands, while allowing the console interface to present whatever is best form a user interaction standpoint and just call the appropriate methods from the Chatr library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants