modulatingforce/forcebot_rs
1
0
Fork 0
Code Issues 33 Pull requests 11 Projects 2 Activity

[ENH] Queue & Evaluate Messages in a Custom Module #34

New issue
Open
opened 2024-03-19 16:07:08 -04:00 by modulatingforce · 1 comment
modulatingforce commented 2024-03-19 16:07:08 -04:00
Owner
Copy link

This will likely be a requirement for Custom Modules

To be able to :

  1. Queue a set of messages (for example, that fit minimum characteristics)

  2. Do evaluation for each message

  3. Respond to only the message in the set that fits certain characteristics

From Ryan

you could queue the last few responses and then after a few seconds respond to the closest guess

Originally posted by @modulatingforce in #1 (comment)

This will likely be a requirement for Custom Modules To be able to : 1. Queue a set of messages (for example, that fit minimum characteristics) 2. Do evaluation for each message 3. Respond to only the message in the set that fits certain characteristics --- From Ryan you could queue the last few responses and then after a few seconds respond to the closest guess _Originally posted by @modulatingforce in https://git.flake.sh/modulatingforce/forcebot_rs/issues/1#issuecomment-238_
modulatingforce added the
Kind/Feature
 label 2024-03-19 16:07:16 -04:00
modulatingforce added this to the Prototype 1.0 milestone 2024-03-19 16:07:21 -04:00
modulatingforce added this to the Rust Learning project 2024-03-19 16:07:23 -04:00
modulatingforce added the
Priority
Medium
 label 2024-03-19 16:07:57 -04:00
modulatingforce added the
Bot_Code
Core
Complexity
Advanced
 labels 2024-03-27 18:33:07 -04:00
modulatingforce modified the project from Rust Learning to Forcebot Prototype 1.0 Push 2024-03-27 18:33:10 -04:00
modulatingforce commented 2024-03-27 18:49:32 -04:00
Author
Owner
Copy link

Setting Low Priority while we're working on Core Features . While this is correctly labeled for Core , the feature here is a low priority feature for Custom developers

Setting Low Priority while we're working on Core Features . While this is correctly labeled for Core , the feature here is a low priority feature for Custom developers
modulatingforce added
Priority
Low
 and removed
Priority
Medium
 labels 2024-03-27 18:49:39 -04:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
TextMods-Module
flake-lock-update
main
cargo-fmt
cargo-fmt-test
Refactor-custom-load
retrieve-reply-details
issue-routine-lock-idea2
issue-routine-lock-idea1
issue-routine-lock
routines-functionality
Log-modules-acts
case-insensitive-objects
20240312_forceplay
No results found.
Labels
Clear 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

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Bug Fix

Branches intended to address an existing Bug

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Nix
  
Ownership
Collab

  
Ownership
Collab with Leads
Collab with one or more Leads

  
Ownership
Individual Lead

  
Ownership
In-Review
Ownership may be in a review or disputed status

  
Ownership
Needs Owner > May Delegate
Tasks that may need reassignment

  
Ownership
Workshop with Leads
Workshop Tasks

  
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
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

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
Milestone
Clear milestone
No items
No milestone
Prototype 1.0
Projects
Clear projects
No items
No project
Forcebot Prototype 1.0 Push
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: modulatingforce/forcebot_rs#34
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?