CHI-3674: Ensure draft case section edits persist in redux #3836
Conversation
… into state. Set this flag when loading cases from a result list, so in progress edits don't get overwritten
…ey are connected. Remove useless test
gpaoloni
left a comment
gpaoloni
left a comment
There was a problem hiding this comment.
One question, but LGTM
| import { connectToCase } from '../../services/ContactService'; | ||
| import { connectToCaseAsyncAction } from '../contacts/saveContact'; | ||
| import { markCaseAsUpdating } from './markCaseAsUpdating'; | ||
| import { referenceCase } from './referenceCase'; |
There was a problem hiding this comment.
I don't get why do we want to reference the case? If the counselor opens the case it will get referenced, so why keep it loaded?
There was a problem hiding this comment.
I think there are times when a contact needs to reference it's associated case without necessarily loading it into the UI. We always reference a case via it's contact if we load up a contact already associated with a case, but we didn't when we initially connected the case, so this resolves that inconsistency
There was a problem hiding this comment.
Ah I think you are right, that's why the "connected case banner" is not clickable when the case is created - this should fix the bug.
Description
Checklist
Other Related Issues
None
Verification steps
AFTER YOU MERGE
You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P