interests
BotCommand #81
Labels
No labels
Automated
Backlog
Post_Prototype_1.0
Bot_Code
Core
Bot_Code
Custom
CI/CD
Complexity
Advanced
Complexity
Basic
Complexity
Expert
Complexity
Intermediate
Kind/Breaking
Kind/Bug
Kind/Bug Fix
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Nix
Ownership
Collab
Ownership
Collab with Leads
Ownership
Individual Lead
Ownership
In-Review
Ownership
Needs Owner > May Delegate
Ownership
Workshop with Leads
Phase 1.0
Requirements > Drafting
Phase 1.0
Requirements > Researching
Phase 1.0
Requirements > Review & Planning
Phase 2.0
Design > Research & Analysis
Phase 3.0
Coding > Implementation
Phase 4.0
QA > Unit Testing & Design
Phase 5.0
Resolution > Completed
Phase 5.0
Resolution > Review for Completion
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: modulatingforce/forcebot_rs#81
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Was thinking of an exercise that maybe @notohh & @Saru could also do and thought of this idea. Maybe thinking of fleshing it out with the group first to see if it's something stupid or we could always code it, and then vote to keep it or not
interests
Bot Command sends to Chat a Script that shows the interests of the Command Invoker, if the Invoker is stored internallyThe Script of the Bot Could be something like the following
An Example Execution & interaction with the Command in Chat could be the following
One way to implement the above is to store the Interests and Messages in a
HashMap
with the key being a String representing the invoker and 2 vectors (?) one for interests and one for messages for eachExercise will be iterating through Vectors and/or HashMaps, so it would be a good exercise
To add regarding the requirement that the Invoker must exist:
we could remove this requirement, and add handling so if the invoker doesn't exist, and the bot responds with a funny general response like "WH OMEGALUL r u?"
at the moment,
custom
modules can't store state variables, so we can't do things like dynamically add or adjust interests (but we can explore these as enhancements later)