-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Debt] Remove applicant filters query #8975
Conversation
@@ -98,73 +100,6 @@ protected function filterToCreateInput(ApplicantFilter $filter) | |||
return $input; | |||
} | |||
|
|||
/** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth repointing these tests at poolCandidateSearchRequest.applicantFilter
instead of removing them? Or am I misunderstanding how this works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that the test testFilterCanBeStoredAndRetrievedWithoutChangingResults()
was querying an applicant filter so I thought why not move the test there and save some space. However, I think your right looking back at it now since it's querying for all the fields which makes for a stronger test. I'll make the changes now 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wow, that was a bit more work than just repointing the tests. 😬 Thanks for pushing through! 🥇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
🤖 Resolves #7654
👋 Introduction
applicantFilter
query🧪 Testing
Assist reviewers with steps they can take to test that the PR does what it says it does.