Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX: Messages: Use "Newest" as default mode #570

Closed
2 tasks done
woile opened this issue Oct 3, 2024 · 2 comments · Fixed by #579
Closed
2 tasks done

UX: Messages: Use "Newest" as default mode #570

woile opened this issue Oct 3, 2024 · 2 comments · Fixed by #579
Labels
area/ux User experiense issues scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Milestone

Comments

@woile
Copy link

woile commented Oct 3, 2024

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

@woile woile added status/triage Issues pending maintainers triage type/feature A brand new feature labels Oct 3, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Oct 3, 2024
Copy link

github-actions bot commented Oct 3, 2024

Hi woile! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

@Haarolean
Copy link
Member

I personally would prefer 'newest first' as well, let's see

@Haarolean Haarolean added type/enhancement En enhancement/improvement to an already existing feature scope/frontend Related to frontend changes and removed type/feature A brand new feature status/triage/manual Manual triage in progress labels Oct 3, 2024
@Haarolean Haarolean linked a pull request Oct 6, 2024 that will close this issue
13 tasks
@Haarolean Haarolean added the area/ux User experiense issues label Oct 6, 2024
@Haarolean Haarolean changed the title Use "Newest" as default mode UX: Messages: Use "Newest" as default mode Oct 6, 2024
@Haarolean Haarolean added this to the 1.1 milestone Oct 6, 2024
@Haarolean Haarolean moved this from Todo to In Review in Release 1.1 Oct 6, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in Release 1.1 Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ux User experiense issues scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants