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

[Bug] Sorting should be done alphabetically by default in the Catalog Content #1038

Closed
dzole0311 opened this issue Jul 9, 2024 · 0 comments
Assignees
Labels
P2 Find a way to fix in the next few sprints regression Signifies a regression issue found during testing

Comments

@dzole0311
Copy link
Collaborator

dzole0311 commented Jul 9, 2024

Context

URL: https://staging.earth.gov/ghgcenter/data-catalog

Blocking a release? (y/n): n

Regression issue? (y/n):
[If yes, add Regression label]

Priority:

Steps to reproduce the issue

  1. Visit the Data Catalog
  2. See that the catalog items are not sorted by the name field
  3. Same for the E&A modal
@dzole0311 dzole0311 added P2 Find a way to fix in the next few sprints regression Signifies a regression issue found during testing labels Jul 9, 2024
@dzole0311 dzole0311 changed the title [Bug] sortField should be by name in Catalog Content [Bug] Sorting should be done alphabetically by default in the Catalog Content Jul 9, 2024
dzole0311 added a commit that referenced this issue Jul 9, 2024
…og (#1039)

**Related Ticket:** #1038

### Description of Changes
Add fix that sorts catalog content alphabetically by default for the
Data Catalog view and the E&A modal. This behavior was there for the
Data Catalog before the last release, but not for the old E&A modal (due
to it using horizontal cards).

### Notes & Questions About Changes
_{Add additonal notes and outstanding questions here related to changes
in this pull request}_

### Validation / Testing
1. The filtering, sorting and search work as before for the Data Catalog
and the E&A modal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Find a way to fix in the next few sprints regression Signifies a regression issue found during testing
Projects
None yet
Development

No branches or pull requests

1 participant