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
Search - Extend Filter Fields #3440
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Terraform plan for meta No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #565 |
Terraform plan for dev No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #565 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 88727a6 |
The performance of the big OR does not seem to be a problem, but it would be nice to do differently. Not today's blocker, though.
jadudm
reviewed
Feb 26, 2024
jadudm
reviewed
Feb 26, 2024
jadudm
reviewed
Feb 26, 2024
danswick
approved these changes
Feb 28, 2024
tadhg-ohiggins
approved these changes
Feb 28, 2024
eazapata23
pushed a commit
that referenced
this pull request
Mar 5, 2024
* Getting search started. * Direct funding search. Rewrite form cleaning. Collapse filters by default. * Linting! * Search on major program. * Linting is for winners * Major program to Y/N field. * Linted! * Minor tests, new field defaults * Linting! * If there aren't eight linting commits, did anything happen? * Adds "Any findings" to the list. The performance of the big OR does not seem to be a problem, but it would be nice to do differently. Not today's blocker, though. * Cleanup, linting, comment removal. * Fiend -> Friend. Not the same! Plus a comment. * Whitespace is not okay, I guess * map -> zip * ALL -> all_findings * apply distinct only to relevant cols --------- Co-authored-by: Matt Jadud <matthew.jadud@gsa.gov> Co-authored-by: Tim Ballard <1425377+timoballard@users.noreply.github.com> Signed-off-by: Edward Zapata <99770283+eazapata23@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Search - Extend Filter Fields
Epic: #3388
Issue: #3407
Changes:
a. Search on findings type. A multi select that allows one to filter by the Y/N fields under the Finding model.
b. Search on Direct/passthrough funding. A multi select that filters on the FederalAward
is_direct
field.c. Search on major_program. A Y/N for the FederalAward
is_major
field. I left this as a Y/N, because we may want it to also highlight the actual program value in the future.def clean_fieldname()
informs.py
, which will automagically fire when callingform.is_valid()
. I included some improvements to ALN & UEI/EIN text field cleaning in this.test_search.py
, in their own class.How to test:
These are non-trivial changes! Some noodling may be required.
Screenshots:
New filters:
Accordions are closed by default (except AY), and 2023 is highlighted by default:
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)git status | grep migrations
. If there are any results, you probably need to add them to the branch for the PR. Your PR should have only one new migration file for each of the component apps, except in rare circumstances; you may need to delete some and re-runpython manage.py makemigrations
to reduce the number to one. (Also, unless in exceptional circumstances, your PR should not delete any migration files.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.