gbowne1 / gbowne1/TwitchBot

[TODO] Server side command configuration

Open
#71 7 comments 4 reactions 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
8
Forks
11
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
Yes. As noted [here](https://github.com/gbowne1/TwitchBot/pull/62#issuecomment-1962423338). Both the client and server would need to be updated each time a command was added. This is suboptimal, to be sure.

**Describe the solution you'd like**
Perhaps a server route hit when the component mounts (not sure what this is called now) or when the app starts? To get an initial config object of available/supported commands and associated API routes?

**Describe alternatives you've considered**
- None. 🚩 — This seems the way to do it though?

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing server route entry points and the client component-mount or app-start entry point mentioned in the issue. Define the command configuration response and its update path, then verify that adding a command no longer requires separate client and server edits.

Written by the indexing model from the issue text.

Assessment

Tech stack
express, javascript, react
Domain
api, backend, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.