Skip to content

fix: 'conversation_parts.assigned_to' property is an object#86

Open
danilofuchs wants to merge 1 commit intosinger-io:masterfrom
danilofuchs:patch-2
Open

fix: 'conversation_parts.assigned_to' property is an object#86
danilofuchs wants to merge 1 commit intosinger-io:masterfrom
danilofuchs:patch-2

Conversation

@danilofuchs
Copy link
Copy Markdown

Description of change

Updated the 'conversation_parts.assigned_to' property to accept an object type in the JSON schema.

The current implementation assumes it is a string, leading to a weird Python Dict representation in the target database:
image

https://developers.intercom.com/docs/references/2.12/rest-api/api.intercom.io/conversations/retrieveconversation
image

Manual QA steps

Risks

  • Breaking current users relying on this field format

Rollback steps

  • revert this branch

AI generated code

https://internal.qlik.dev/general/ways-of-working/code-reviews/#guidelines-for-ai-generated-code

  • this PR has been written with the help of GitHub Copilot or another generative AI tool

Updated the 'assigned_to' property to accept an object type in the JSON schema.

The current implementation converts a Python dict to text
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.

1 participant