Message.pyについて
Open
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Messageって命名だとどういう処理が入ってるかわかりずらいかな
例えばdiscord.Messageみたいな独自のMessageクラスがありそうに見えるかも?
そもそもこのファイル、choice_Message以外に処理がなくて目的が微妙。
消してon_messageに書くのもありだし、メッセージを受け取って各commandの関数を実行する役割とか持たせたりとかでもいいかな
Contributor guide
No contributing guide indexed for this repository
Research direction
Read Message.py and the on_message entry point to understand the current choice_Message flow and how commands are invoked. Before changing code, clarify whether the goal is to remove Message.py or give it responsibility for dispatching messages to command functions. Done means the selected structure is implemented and the existing message-to-command behavior still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100