-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[new_profile] Site not selected when recruiting another candidate #9197
Conversation
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 believe this is a typo
// on whether the user clicked on 'Access Profile' or | ||
// 'Recruit another candidate' respectively | ||
window.location.href = result.value === true | ||
? window.location.href = '/' + data.CandID |
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.
? window.location.href = '/' + data.CandID | |
? '/' + data.CandID |
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.
@jeffersoncasimir You're absolutely right! The funny thing is, the code works, but your version is cleaner/simpler. Ready for another review.
Works as expected! |
This PR ensures that if a user is associated to only one site and creates two candidates in a row, his/her site will be automatically selected on the new profile form when the form is first displayed and when he/she clicks on 'Recruit another candidate'. It also updates the module's test plan to cover this scenario.
Fixes #9146