Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync - Strange behavior #396

Open
drazen-janjicek opened this issue Nov 10, 2024 · 0 comments
Open

Sync - Strange behavior #396

drazen-janjicek opened this issue Nov 10, 2024 · 0 comments
Assignees

Comments

@drazen-janjicek
Copy link

drazen-janjicek commented Nov 10, 2024

Hello, I'm experiencing some behavior of the Sync Api that I cannot really understand (when comparing with the Api docs).

  • Init
    Init should reset the sync and retrieve all items on the Sync call with the new token. However, it's returning nothing if there are no new changes.

  • Sync returns only last change
    On my local environment I'm calling sync and retrieving 1 item. With the new token I call again sync and get the same item but with a newer timestamp. I expect to get only the last change.

  • Sync returns old changes
    I'm testing the Api with a console app and store the current token on the filesystem. When I call sync with the most recent token, I would expect the api to return nothing results if there are no changes in the CMS since the previous sync. Sometimes this works, but most of the time I get items back. Is this some caching here? Since it's a console app and I restart it the local cache in de client should be clean.

  • Strongly typed data
    This value is always null. Since sync sits on top of delivery, how can I retrieve strongly-typed items in the response? Can't find any documentation.

I'm using the latest delivery nuget packages with .Net 8

@pokornyd pokornyd self-assigned this Nov 14, 2024
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

No branches or pull requests

2 participants