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

Store flair in user document as reference to flair DB collection. #47

New issue
Closed
opened 2024-11-26 08:28:05 -05:00 by rainbownapkin · 1 comment
rainbownapkin commented 2024-11-26 08:28:05 -05:00 (Migrated from gitlab.com)
Copy link

The user's current flair is stored as a string. While it makes sense to store the name of the flair as a string within connectedUser.js when they're connected, it should be pulled from a populated DB reference instead of a string that gets checked when it's changed.

If implemented properly, this should introduce no performance penalties over the current system.

The user's current flair is stored as a string. While it makes sense to store the name of the flair as a string within connectedUser.js when they're connected, it should be pulled from a populated DB reference instead of a string that gets checked when it's changed. If implemented properly, this should introduce no performance penalties over the current system.
rainbownapkin commented 2024-12-03 06:34:52 -05:00 (Migrated from gitlab.com)
Copy link

Updated userSchema to store flair as db ref: 279640a7

Updated userSchema to store flair as db ref: 279640a7
rainbownapkin (Migrated from gitlab.com) closed this issue 2024-12-03 06:34:54 -05:00
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
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#47
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?