rainbownapkin/canopy
1
0
Fork 0
Code Issues 2 Pull requests Actions Packages Projects Releases Wiki Activity

per-channel !toke commands w/ management panel in channel settings #58

New issue
Closed
opened 2024-12-10 21:07:48 -05:00 by rainbownapkin · 4 comments
rainbownapkin commented 2024-12-10 21:07:48 -05:00 (Migrated from gitlab.com)
Copy link
No description provided.
rainbownapkin commented 2024-12-10 21:07:49 -05:00 (Migrated from gitlab.com)
Copy link

added #23 as parent issue

added #23 as parent issue
rainbownapkin commented 2024-12-10 22:29:48 -05:00 (Migrated from gitlab.com)
Copy link

Per-channel toke commands should be stored in-ram within the activeChannel class, loaded upon channel activation and whenever the tokeCommands array within the channel document is altered.

This will prevent constant database access every time someone takes a toke, because doing that is fucking ridiculous.

Per-channel toke commands should be stored in-ram within the activeChannel class, loaded upon channel activation and whenever the tokeCommands array within the channel document is altered. This will prevent constant database access every time someone takes a toke, because doing that is fucking ridiculous.
rainbownapkin commented 2024-12-15 09:53:14 -05:00 (Migrated from gitlab.com)
Copy link

Added per-channel toke commands to the back end, as well as related browser-side ajax call helper functions: a1fbbea7b7

Now to replicate the toke command management panel from the adminPanel in the channelSettings page.

Added per-channel toke commands to the back end, as well as related browser-side ajax call helper functions: a1fbbea7b76dc30bf3559da766577d889b91fb19 Now to replicate the toke command management panel from the adminPanel in the channelSettings page.
rainbownapkin (Migrated from gitlab.com) closed this issue 2024-12-15 11:07:58 -05:00
rainbownapkin commented 2024-12-15 11:07:59 -05:00 (Migrated from gitlab.com)
Copy link

Finished up with per-channel !toke command panel in channel settings page: 169b863965

Finished up with per-channel !toke command panel in channel settings page: 169b8639650a5c7669a1768250df205f2afd72c0
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
0.4-indev-hotfix-3
0.4-indev-hotfix-2
0.4-indev-hotfix-1
0.4-indev
0.3-indev-hotfix-1
0.3-indev
verbose-queue
0.2-indev
0.1-indev
No results found.
Labels
Clear labels   
Bug

   
Cleanup/Refactor

   
Core Feature

   
Documentation

   
Feature

   
Performance Improvement

   
Security Improvement

   
UX/Accessibility

   
Unreproducable Bug
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
Milestone
Clear milestone
No items
No milestone
Canopy v0.1-Indev
Projects
Clear projects
No items
No project
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: rainbownapkin/canopy#58
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?