Mark as read 'lastReadEntryId' wrong direction

[Stefan Nienhuis]

Hi there,

I'm having an issue with marking a category as read when using the 'lastReadEntryId'. If for example this would be the data returned from the stream request:

[
  {
    "id": "1"
  },
  {
    "id": "2"
  },
  {
    "id": "3"
  },
  {
    "id": "4"
  },
  {
    "id": "5"
  }
]

And I would mark as read and set lastReadEntryId to "3", articles 3, 4 and 5 are marked as read. But my app shows the articles from top to bottom, so articles 1, 2 and 3 are shown, then the user presses mark as read, and those should be marked as read. Is this the intended behaviour or am I doing something wrong? If so, could someone explain how to correctly mark those articles as read?

Thanks in advance,

Stefan Nienhuis

[David Chatenay]

  Hi,

  Whether you pass a timestamp or an entry id, the server marks entries older than this timestamp/entry as read.

  If you want to mark entries newer than the timestamp/entry as read, you must mark individual entries (1, 2, and 3 in your example) as read.

  Hope this helps

-- 

David Chatenay

Platform Engineer

Feedly

--
You received this message because you are subscribed to the Google Groups "Feedly Cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email to feedly-cloud...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/feedly-cloud/b98a9804-9afb-470f-89e1-51ae2e7d124d%40googlegroups.com.