Vote: Default Sorting #32
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
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
Unraid
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: FrederikBaerentsen/BrickTracker#32
Loading…
Reference in New Issue
Block a user
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?
Currently the front page default sorting is by "added". Meaning first set added to the database is first.
Personally this isn't ideal.
Vote for your favorite:
.env
to customize this 👀I voted to have a setting for it, but there still needs a default value of course.
Not sure which I like best.
How about adding the option “by date added - most recent first.”
This Way, whenever adding a New set, the recently added set Will be on top of the list, giving you an easy visual control that it was correctly added.
Of course, this kind of Quality Control check, should ideally happen when searching for adding the set, before actually adding to database, but that kind of feature might be Way Down the Line (understandably).
So this could be a Nice intermediate Way to give people the option to do this.
Will also mane most recent show on top, which I kind of Think makes sense.
Implemented in
e2425a106a
using: