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

Fix browse-by-date year filter option generation #2809

Closed
wants to merge 1 commit into from

Conversation

bkeese
Copy link

@bkeese bkeese commented Feb 14, 2024

Empty issued dates incorrectly defaulted to current year instead of lower year limit, resulting in zero year options for the year picker, in turn resulting in a page that never finishes loading.

References

Fixes #2808

Description

A bug in the logic of the browse-by-date year picker resulted in the Browse by Issue Date page never loading.

Instructions for Reviewers

Ensure Browse by Issue Date still works as expected.
Items with empty dc.date.issued should default to the configured browseBy.defaultLowerLimit, not the current year.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using yarn lint
  • My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

Empty issued dates incorrectly defaulted to current year instead of lower year limit, resulting in zero year options for the year picker, in turn resulting in a page that never finishes loading.
@tdonohue tdonohue added bug component: Discovery related to discovery search or browse system 1 APPROVAL pull request only requires a single approval to merge port to dspace-7_x This PR needs to be ported to `dspace-7_x` branch for next bug-fix release labels Feb 14, 2024
@tdonohue
Copy link
Member

As I noted in the original ticket, I'm finding this PR isn't working properly for me. Just wanting to make sure that feedback is also tracked here. See comments at #2808 (comment)

@bkeese
Copy link
Author

bkeese commented Mar 1, 2024

I plan to make one small tweak to this PR so it handles both cases of missing issue dates. I'll try to do it today.

EDIT: Actually, I am not going to do this yet because this PR seems to fix the problem: #2832

@tdonohue tdonohue self-requested a review March 21, 2024 15:57
@tdonohue
Copy link
Member

Closing, as this bug was just fixed by #2832 , so this PR is no longer needed. See #2808 (comment)

@tdonohue tdonohue closed this Mar 29, 2024
@tdonohue tdonohue removed the port to dspace-7_x This PR needs to be ported to `dspace-7_x` branch for next bug-fix release label Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 APPROVAL pull request only requires a single approval to merge bug component: Discovery related to discovery search or browse system
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Browse by Issued Date hangs
2 participants