Skip to content

Conversation

patricijabrecko
Copy link
Collaborator

No description provided.

Copy link

@tjazerzen tjazerzen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking better :). Providing complete context and avoid "guessing" is key to developing scalable integrations with plain. In some places, I saw missing context, and it's very important to address this before rendering.

- If "event_type" equals "EXTRACTION_DATA_START" or "EXTRACTION_DATA_CONTINUE" The Extraction Function should push the 'tasks' and 'users' data. To push the 'tasks' data, it should:
- If `TheExtractionStateObject["tasks"]["completed"]=false`:
- While Fetching The Fetched Tasks using pagination (The Tasks Iteration):
- When fetching The Fetched Tasks use the query param 'fields', where the value is an array of strings, which contains at least 'hasAttachments'.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this still have to be adjusted to comment made in the previous review iteration.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I think this is described correctly - it has to at least contain 'hasAttachments', can also contain other values. Depends on the use case.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I limit it here to contain only 'hasAttachments' it will be in conflict with other FRs.

Copy link

@tjazerzen tjazerzen Oct 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest you phrase which contains at least 'hasAttachments'. less ambiguously as we discussed, and render. I understand you got a conflict earlier. I think we should get to the root cause of the problem why a conflict exists, and then resolve it.

Copy link

@tjazerzen tjazerzen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright 👍

Let's finish it tomorrow, but here are the things you can do right away:

  • final touches for mappings/ folder
  • Minor updates to test_data/ folder

Also, I'm missing the updates for the new templating:

  • every file from mappings/ folder
  • Correct templating of templates/chef_cli_normalization_validation.plain in devrev-wrike-snapin.plain

- If "event_type" equals "EXTRACTION_DATA_START" or "EXTRACTION_DATA_CONTINUE" The Extraction Function should push the 'tasks' and 'users' data. To push the 'tasks' data, it should:
- If `TheExtractionStateObject["tasks"]["completed"]=false`:
- While Fetching The Fetched Tasks using pagination (The Tasks Iteration):
- When fetching The Fetched Tasks use the query param 'fields', where the value is an array of strings, which contains at least 'hasAttachments'.
Copy link

@tjazerzen tjazerzen Oct 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest you phrase which contains at least 'hasAttachments'. less ambiguously as we discussed, and render. I understand you got a conflict earlier. I think we should get to the root cause of the problem why a conflict exists, and then resolve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants