From 3db1cd258f71a5e40777b5ec41897d484344d3ec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ga=C5=A1per=20Zgonec?= Date: Wed, 8 Oct 2025 14:52:05 +0200 Subject: [PATCH] Fixed the events present in the template. --- devrev-snapin-template.plain | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devrev-snapin-template.plain b/devrev-snapin-template.plain index b862479..31d7100 100644 --- a/devrev-snapin-template.plain +++ b/devrev-snapin-template.plain @@ -106,7 +106,7 @@ - Test The Function using the resource [external_sync_unit_check.json](test_data/external_sync_unit_check.json). Test is successful if The Callback Server receives from DevRev an event with "event_type" that equals "EXTRACTION_EXTERNAL_SYNC_UNITS_DONE". The test must not send the event directly to The Callback Server. - Implement The Function called "data_extraction_check" (The Data Extraction Check Function) that provides a test of the 'data extraction' part of the extraction workflow as described in the resource [data-extraction.md](docs/data-extraction.md). The Data Extraction Check Function should: - - if "event_type" equals "EXTRACTION_DATA_START" or "EXTRACTION_ATTACHMENTS_CONTINUE", The Data Extraction Check Function should: + - if "event_type" equals "EXTRACTION_DATA_START" or "EXTRACTION_DATA_CONTINUE", The Data Extraction Check Function should: - Initialize a single repo "users" - normalize the users data using The Normalization Function - push the normalized users data to The DevRev Servers