Closed nickevansuk closed 2 years ago
Also note that a common error is for Slot
s to reference FacilityUse
@id
instead of IndividualFacilityUse
@id
when there's IndividualFacilityUse
s present within the FacilityUse
s in the feed.
So the logic here should exclusively use IndividualFacilityUse
s if they exist, and hence it should not match a Slot
to a FacilityUse
if it has IndividualFacilityUse
s.
The broker-microservice does not currently track
IndividualFacilityUseSlot
The following is an example of a
Slot
for anIndividualFacilityUse
within aFacilityUse
represented in a C1 response:The broker-microservice should extract this from a feed pair such as the example specified here and here.
However, it currently does not recognise the embedded
individualFacilityUse
array in theFacilityUse
feed.Implementation hints
Consider how
ingestParentOpportunityPage
andingestOpportunityPage
should work considering the multiple embeddedindividualFacilityUse
array in the parent opportunity feed.Testing the fix
The following should succeed if this fix is made successfully
Additionally the GET request shown here should return the
Slot
->IndividualFacilityUse
->FacilityUse
model in the JSON example above (rather than theSlot
->FacilityUse
model shown at the link to the test suite output). Note the test suite doesn't need to be run to prove this, the GET request can be created manually using anySlot
@id
from the feed.To speed up development, it might be helpful to turn off
waitForHarvestCompletion
. If the fix works, then once the broker-microservice has consumed the relevantFacilityUse
with embedded matchingIndividualFacilityUse
for theSlot
, theGET
request above should then successfully return with the model in the JSON example above.