Change Details

Created a thick thread with 100 messages. Closed and reopened the app, scrolled up, and made sure all 100 messages are displayed. There are two issues though: 1. We don't stop after fetching the first batch. Instead, we're fetching all the batches one by one immediately. - created an issue to track https://linear.app/comm/issue/ENG-9097/fetching-new-messages-in-message-list-is-glitchy-when-it-happens 2. The robotext about creating a thread isn't fetched when there are more than `defaultNumberPerThread` messages. - fixed. The issue was that we were always throwing away the last message, even in the last batch.

On web: Created a thick thread with 100 messages. Closed and reopened the app, scrolled up, and made sure all 100 messages are displayed. There are two issues though: 1. We don't stop after fetching the first batch. Instead, we're fetching all the batches one by one immediately. - created an issue to track https://linear.app/comm/issue/ENG-9097/fetching-new-messages-in-message-list-is-glitchy-when-it-happens 2. The robotext about creating a thread isn't fetched when there are more than `defaultNumberPerThread` messages. - fixed. The issue was that we were always throwing away the last message, even in the last batch. On native: Created a thick thread with 100 messages. Closed and reopened the app, scrolled up, and made sure all 100 messages are displayed. This time issue 1. from the web isn't present because fetching (or updating the UI) is a lot slower.

On web: Created a thick thread with 100 messages. Closed and reopened the app, scrolled up, and made sure all 100 messages are displayed. There are two issues though: 1. We don't stop after fetching the first batch. Instead, we're fetching all the batches one by one immediately. - created an issue to track https://linear.app/comm/issue/ENG-9097/fetching-new-messages-in-message-list-is-glitchy-when-it-happens 2. The robotext about creating a thread isn't fetched when there are more than `defaultNumberPerThread` messages. - fixed. The issue was that we were always throwing away the last message, even in the last batch. On native: Created a thick thread with 100 messages. Closed and reopened the app, scrolled up, and made sure all 100 messages are displayed. This time issue 1. from the web isn't present because fetching (or updating the UI) is a lot slower.