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

Fixes/121 search textfield update #153

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

eddiesarevalo
Copy link
Member

@eddiesarevalo eddiesarevalo commented Jan 27, 2025

🗒️ Summary

This PR fixes the following issues:

  • Using back/forward buttons on search results page does not update the text in the search textfield
  • Selecting multiple dropdowns in homepage doesn’t show on search correctly. The results not found message that allows removal doesn’t render right.
  • Clicking x on a selected dropdown in search will show “0 selected” instead of all on the home page.
  • all still shows in page_type search page.
  • On the home page, if returning from back,then selecting a checkbox and searching again will clear out the text from the url causing a new search to omit the search text.
  • Certain search text for example "arecibo" will just cause a crash.

⚙️ Test Data and/or Report

Build has been tested. Run this branch with wds-react develop branch. Test for the above bugs by attempting to replicate issue.

♻️ Related Issues

-Added fix to update search box when navigating from back or forward in history.
-Added fix for invalid investigation lids causing crash. Example search for "arecibo"
-Added fix to keep the value of the search text when returning from the back button and then selecting a new checkbox.
-Fixed the message that shows on the search page when unrelated filters are selected from the home page.
-Fixed the label showing as "0 selected" instead of "all" when the filter chip X button is clicked.
-The "all" checkbox is now shown as checked when all chips are deselected.
-The all value is removed from single select filters since it should not be able to be selected. It is already acting as if all is selected when nothing is selected.
@eddiesarevalo eddiesarevalo requested a review from a team as a code owner January 27, 2025 23:17
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
22.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

@eddiesarevalo
Copy link
Member Author

eddiesarevalo commented Jan 28, 2025

Sonarcloud code analysis says to use if/else statements but in the referenced article explicitly says Sonar rule for nested ternaries does not apply to JSX. The reason being JSX doesn't allow for if/else statements. Will leave as is since it is clear from JSX what is going on. It picked up the code as Javascript instead of JSX

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.

Using back/forward buttons on search results page does not update the text in the search textfield
1 participant