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

[Issue #1494] Modify agency filter to be an exact match #1530

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

chouinar
Copy link
Collaborator

Summary

Fixes #1494

Time to review: 2 mins

Changes proposed

Adjust the logic for filtering by agency to be an exact match instead of the prior "starts with" logic.

Context for reviewers

This adjustments comes out of a recent discussion with our front-end folks. Turns out they intend to pass us every agency for sub-agencies (eg. HHS-123, HHS-456, etc). I had implemented sub-agency logic assuming we'd want prefixes, which is clunky. This makes the logic more intuitive by just being a simple match.

Note that previously the agencies were also case-insensitive which is no longer here, but that also isn't really necessary.

Additional information

Updated a few tests that assumed prior logic - nothing too significant here

Copy link
Collaborator

@coilysiren coilysiren left a comment

Choose a reason for hiding this comment

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

Makes sense! 👍🏼

@chouinar chouinar merged commit 5d898f9 into main Mar 27, 2024
9 checks passed
@chouinar chouinar deleted the chouinar/1494-adjust-agency-filter branch March 27, 2024 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Task]: Modify agency filter to do exact matches rather than the strbegins approach we have
2 participants