-
Notifications
You must be signed in to change notification settings - Fork 1
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
RAS-1289 Update the way claims is determined in the party service #435
Conversation
/deploy crockers |
Deploying to dev cluster with following parameters:
|
/deploy wilkia |
Deploying to dev cluster with following parameters:
|
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 good, one bit of housekeeping
What and why?
This PR updates how claims are processed and introduces survey_id in the check. This is part of a larger piece of reducing the amount of 139 crashes, at present get_respondent_by_id is doing more that what it should and by calling to_respondent_with_associations_dict() causing considerable overhead leading to timeouts. I can't remove get_respondent_by_id or the dict it is generating, but I can move the functionality to a cleaner function which just returns the repondent and then make enrolment checks cleaner and far more efficient
How to test?
Test in conjunction with ONSdigital/ras-secure-message#428, trying sending a new email via the survey help route, the account help route and replying to an existing thread. Reply and create a new message in ROPs as well
Jira