Skip to content

Conversation

@jazairi
Copy link
Contributor

@jazairi jazairi commented Nov 3, 2025

Why these changes are being introduced:

USE UI uses a different search form partial than
GeoData. When this change was made, we did not
update the form partial loaded in the full record
view.

Relevant ticket(s):

How this addresses that need:

This updates the record_geo partial to load the form_geo partial.

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

To confirm, execute a search with the GeoData feature enabled and click a result title to get to the full record view. The search form above the record should be the advanced search form with geospatial fields, not the simple search form from USE.

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.

@jazairi jazairi requested a review from JPrevost November 3, 2025 17:39
@mitlib mitlib temporarily deployed to timdex-ui-pi-use-157-b4wmkru6s November 3, 2025 17:41 Inactive
@coveralls
Copy link

coveralls commented Nov 3, 2025

Pull Request Test Coverage Report for Build 19074153354

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 19073615669: 0.0%
Covered Lines: 859
Relevant Lines: 874

💛 - Coveralls

@JPrevost JPrevost self-assigned this Nov 4, 2025

<%= render(partial: 'shared/site_title') %>
<%= render(partial: 'search/form')%>
<%= render(partial: 'search/form_geo')%>
Copy link
Member

Choose a reason for hiding this comment

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

This makes me nervous that all full record views will use the geo form when we move in that direction. Is there a reason to not wrap this in our feature check like we do in other places in this template?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point. I didn't bother since GeoData is the only app using that feature, but I suppose USE UI will at some point, too.

@jazairi jazairi requested a review from JPrevost November 4, 2025 15:20
@jazairi jazairi temporarily deployed to timdex-ui-pi-use-157-b4wmkru6s November 4, 2025 15:20 Inactive
Why these changes are being introduced:

USE UI uses a different search form partial than
GeoData. When this change was made, we did not
update the form partial loaded in the full record
view.

Relevant ticket(s):

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

How this addresses that need:

This updates the `record_geo` partial to load the `form_geo` partial
when the GeoData feature is enabled.

Side effects of this change:

None.
@jazairi jazairi temporarily deployed to timdex-ui-pi-use-157-b4wmkru6s November 4, 2025 15:38 Inactive
@jazairi jazairi merged commit fcc9116 into main Nov 4, 2025
5 checks passed
@jazairi jazairi deleted the use-157 branch November 4, 2025 15:39
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.

6 participants