-
-
Notifications
You must be signed in to change notification settings - Fork 203
Closed
Labels
area/uxUser experiense issuesUser experiense issuesscope/frontendRelated to frontend changesRelated to frontend changesstatus/triage/completedAutomatic triage completedAutomatic triage completedtype/enhancementEn enhancement/improvement to an already existing featureEn enhancement/improvement to an already existing feature
Milestone
Description
Issue submitter TODO list
- I've searched for an already existing issues here
- I'm running a supported version of the application which is listed here and the feature is not present there
Is your proposal related to a problem?
Most of the time, we have experienced that users want to see the newest first
Describe the feature you're interested in
In here:
| const defaultModeValue = ModeOptions[0].value; |
Use default 1, which would be latest
Describe alternatives you've considered
Making it a configuration parameter, but I think "Newest" is good enough. I'd like to check here if everyone also agrees that Newest as default would be the best default.
Version you're running
1.0.0
Additional context
No response
fallen-up, Haarolean and polegkashti
Metadata
Metadata
Assignees
Labels
area/uxUser experiense issuesUser experiense issuesscope/frontendRelated to frontend changesRelated to frontend changesstatus/triage/completedAutomatic triage completedAutomatic triage completedtype/enhancementEn enhancement/improvement to an already existing featureEn enhancement/improvement to an already existing feature