DevChatter / DevChatter/DevChatterBot
Commands Break when Namespaces Change
Open
bug
good first issue
- Dominant language
- JavaScript
- Stars
- 54
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Existing commands in the bot already will stop working right if you change their type name or move them to a new namespace. We should make sure to compare the list of aliases on startup to make sure they're valid. If not, we should fix them.
On startup, we add commands to the alias table. We need to make sure that it either fixes or adds a new entry for commands whose name or namespace change.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.