Skip to content

Conversation

@jazairi
Copy link
Contributor

@jazairi jazairi commented Oct 30, 2025

Why these changes are being introduced:

UXWS would like the search tabs to display at the
bottom of the header, below the search form.

Relevant ticket(s):

How this addresses that need:

This moves the tabs to a partial, which is then rendered in the search form if results are present. No additional conditional logic is required, because the form itself is rendered only if the GeoData feature is not enabled.

Side effects of this change:

None.

Developer

Accessibility
  • ANDI or WAVE has been run in accordance to our guide.
  • This PR contains no changes to the view layer.
  • New issues flagged by ANDI or WAVE have been resolved.
  • New issues flagged by ANDI or WAVE have been ticketed (link in the Pull Request details above).
  • No new accessibility issues have been flagged.
New ENV
  • All new ENV is documented in README.
  • All new ENV has been added to Heroku Pipeline, Staging and Prod.
  • ENV has not changed.
Approval beyond code review
  • UXWS/stakeholder approval has been confirmed.
  • UXWS/stakeholder review will be completed retroactively.
  • UXWS/stakeholder review is not needed.
Additional context needed to review

Please confirm that tabs continue not to show in GeoData.

Code Reviewer

Code
  • I have confirmed that the code works as intended.
  • Any CodeClimate issues have been fixed or confirmed as
    added technical debt.
Documentation
  • The commit message is clear and follows our guidelines
    (not just this pull request message).
  • The documentation has been updated or is unnecessary.
  • New dependencies are appropriate or there were no changes.
Testing
  • There are appropriate tests covering any new functionality.
  • No additional test coverage is required.

Why these changes are being introduced:

UXWS would like the search tabs to display at the
bottom of the header, below the search form.

Relevant ticket(s):

* [USE-147](https://mitlibraries.atlassian.net/browse/USE-147)

How this addresses that need:

This moves the tabs to a partial, which is then rendered in the search
form if results are present. No additional conditional logic is
required, because the form itself is rendered only if the GeoData
feature is not enabled.

Side effects of this change:

None.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 18952428765

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 98.284%

Totals Coverage Status
Change from base Build 18945862716: 0.0%
Covered Lines: 859
Relevant Lines: 874

💛 - Coveralls

@mitlib mitlib temporarily deployed to timdex-ui-pi-use-147-mo-szsiis October 30, 2025 19:17 Inactive
@jazairi jazairi requested a review from djanelle-mit October 30, 2025 19:18
@matt-bernhardt matt-bernhardt self-assigned this Oct 31, 2025
Copy link
Member

@matt-bernhardt matt-bernhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I activate the geodata feature on the review app, I still don't see the tab partial - so that seems to be okay.

+1 to having the tabs be in a partial, that feels better. While I wonder about the eventual naming convention we're going to use, and how easy it will be to adopt that terminology for things like tab names and URL anchors, I don't see a better choice available to us right now.

:shipit:

@jazairi jazairi merged commit 17e522b into main Oct 31, 2025
5 checks passed
@jazairi jazairi deleted the use-147-move-tabs branch October 31, 2025 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants