fix(chat): Add a repair-step to handle the last-read-message=0 case #13951
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
Repair step doc block
completely unread. This meant that the next time a client/browser loaded the
chat it would start all from the beginning. However, there were various
issues over the time that made the frontend getting
null
orundefined
into the wrong place and then accidentally loading 8 years of chat from the
beginning. So it was agreed that the frontend manually blocks loading with
last-read-message=0 and the special cases use -2 for this situation.
🛠️ API Checklist
🏁 Checklist
docs/
has been updated or is not required