replaced Minio with Document Record Service #760
Conversation
flutistar
requested review from
severinbeauvais,
cameron-eyds and
doug-lovett
There was a problem hiding this comment.
Looks good Brandon!
I have a few questions around the state management of consumerDocumentId.
Are we storing this in state because we are using it in subsequent document requests?
ie the first POST generates the docId and we use that affiliate all the following documents to that singular docId?
If so, it makes sense in state, that being said we may want to consider that this property will need to be cleared before the Cont-In flow is launched or exited etc.
Either way, we will want to make sure this ID doesn't persist between Cont In Filings.
Edge case for sure and maybe the state IS already reset between, just wanted to call it out!
src/interfaces/store-interfaces/state-interfaces/continuation-in-state-interface.ts
Show resolved
Hide resolved
flutistar
requested review from
cameron-eyds,
JazzarKarim,
doug-lovett and
severinbeauvais
| @@ -4,4 +4,5 @@ export interface AuthorizationProofIF { | |||
| fileKey: string | |||
| fileName: string | |||
| }> | |||
| consumerDocumentId?: string | |||
There was a problem hiding this comment.
Can we make this name consistent with documentServiceId (in filing-interfaces.ts and elsewhere)?
There was a problem hiding this comment.
We have both documentServiceId and consumerDocumentId as well.
Thanks
There was a problem hiding this comment.
I was thinking about this documentServiceId + documentConsumerId.
Is the first one "service id" and second one "document id"? If yes then what you have makes sense.
flutistar
merged commit 4d640b7
into
bcgov:feature-drs-integration
Issue #: /bcgov/entity#23446
Description of changes:
AuthorizationProofcomponentUnlimitedLiabilityCorporationInformationcomponentconsumerDocumentIdBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).