Skip to content

Conversation

@jakeminard
Copy link
Collaborator

CG-14844: Graph Source SDK - Journal Id Not Returned

When something is synced in graph-source-sdk, the content will go through _stream. To be able to know the status for the synced content, we would need to be able to see the return from the service, but this is not happening in SaveContentAsync.

The response body looks like this:
image

With the information, a developer would be able to see why sync is failing by hitting this path (while being authenticated).

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR modifies the Graph Source SDK to return journal IDs from the SaveContentAsync method, enabling developers to track sync status by accessing the stream endpoint. Previously, the method returned an empty string regardless of the API response.

  • Added ContentV2ApiResponse model to capture journal ID from API responses
  • Modified SaveContentAsync to parse and return the journal ID from the response
  • Updated unit tests to verify the new response handling behavior

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
ContentV2ApiResponse.cs New model class to capture journal ID from API responses
GraphSourceRepository.cs Modified SaveContentAsync to return journal ID instead of empty string
GraphSourceRepositoryTests.cs Updated existing tests and added new test to verify journal ID return behavior

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Copy link

@hieu-opti hieu-opti left a comment

Choose a reason for hiding this comment

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

Approved.

Tests were executed and passed
New tests added locally to address edge cases passed

@jakeminard jakeminard merged commit c75c680 into main Sep 12, 2025
1 check passed
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.

4 participants