ykzheng
The
lastUpdate
value in the highlights field of the https://api.raindrop.io/rest/v1/raindrop/{id} endpoint is always the same as the
lastUpdate
of the article. If a new highlight is added to the article, the
lastUpdate
field of the old highlights is changed to the
lastUpdate
of the article.
This bug breaks the syncing feature that only syncs the updated highlights.
Expected behavior:
The
lastUpdate
of the highlight should not be changed if no update is made to the highlight entry.
Reproduce flow:
  1. Make some highlights in an article in raindrop
  2. Put the article in the specific collection (e.g., "Test" for example) and get the id of the "Test" collection using https://api.raindrop.io/rest/v1/collections endpoint
  3. Get the id of the article using https://api.raindrop.io/rest/v1/collection/{id} endpoint
  4. Query https://api.raindrop.io/rest/v1/raindrop/{id} to check the lastUpdate field in the
    highlights
    field
  5. Make new additional highlights in the same article
  6. Query https://api.raindrop.io/rest/v1/raindrop/{id} to check the lastUpdate field in the
    highlights
    field