Future post dates - #26
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a9647a1750
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const FEED_TIMELINE_CACHE_FILENAME_PREFIX = 'RecentEntries'; | ||
| const FEED_ICONS_CACHE_FILENAME = 'Icons.json'; | ||
| const FEED_TIMELINE_CACHE_VERSION = 1; | ||
| const FEED_TIMELINE_CACHE_VERSION = 2; |
There was a problem hiding this comment.
When users update with pending offline/failed read or bookmark changes saved in the v1 timeline cache, this version bump makes normalize_timeline_cache_payload reject the whole payload before restore_local_entry_state_from_cache can restore the local_*_entry_ids, so bootstrap falls back to the server unread/starred state and those queued local actions are never retried. If the entry snapshots need invalidating to recompute future dates, please still migrate the local ID arrays or invalidate only the entries.
Useful? React with 👍 / 👎.
1 participant
Fixed the bucketing of dates. Now using
created_atmore.