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

Default sort order of notifications page #6327

Merged
merged 1 commit into from
Sep 20, 2023
Merged

Conversation

bbpennel
Copy link
Contributor

Fixes

None, committing back a local override

Summary

Changes the default sort order on the notifications page to sorting in descending order by timestamp, so that newest notifications display first.

Guidance for testing, such as acceptance criteria or new user interface behaviors:

Visit the notifications page by clicking the notification counter at the top of the page. Observe that without this PR the notifications display oldest notifications first. With this PR, the new notifications are displayed first.

Type of change (for release notes)

notes-bugfix - default the notifications page to display newest entries first

Detailed Description

This was a local override in our repository that was requested so that users wouldn't have to page through all their old notifications to see recent activity. While updating overrides, I figured it would make sense to offer it back in case it was useful more broadly.

Changes proposed in this pull request:

Sets a default sort for datatables in the html of the notifications table.

@samvera/hyrax-code-reviewers

…p, so that newest notifications display first
@dlpierce dlpierce merged commit 04271c4 into main Sep 20, 2023
4 checks passed
@dlpierce dlpierce deleted the sort-notifications-desc branch September 20, 2023 14:44
@dlpierce dlpierce added the notes-minor Release Notes: Non-breaking features label Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notes-minor Release Notes: Non-breaking features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants