Change Details

This makes the `lastPruned` field optional for thread activity entries. Currently, we populate thread activity entries lazily, and so the type should reflect that lastPruned is optional. Context: https://linear.app/comm/issue/ENG-7663/missing-lastpruned-field-in-current-thread-activity-redux-persist#comment-d17294bb

This makes the `lastPruned` or `lastNavigatedTo` type field optional for thread activity entries (both empty is not possible). Currently, we populate thread activity entries lazily, and so the type should reflect that either field is optional. Context: https://linear.app/comm/issue/ENG-7663/missing-lastpruned-field-in-current-thread-activity-redux-persist#comment-d17294bb

This makes the `lastPruned` or `lastNavigatedTo` type field optional for thread activity entries (both empty is not possible). Currently, we populate thread activity entries lazily, and so the type should reflect that lastPrunedeither field is optional. Context: https://linear.app/comm/issue/ENG-7663/missing-lastpruned-field-in-current-thread-activity-redux-persist#comment-d17294bb