Change Details

Introduce `deprecatedConvertClientDBThreadInfoToRawThreadInfo` which turns a ClientDB representation of `RawThreadInfo` into `LegacyRawThreadInfo`. The reason for this function, as described in D10198, is to maintain correctness of existing Redux migrations. (As an aside, Redux migrations would be a great thing to write unit tests for because often our assumptions about "current state of the codebase" when modifying helper functions don't apply to migrations and can break them. I just happened to notice `convertClientDBThreadInfoToRawThreadInfo` when looking at creating a new Redux migration and realized this would break old migrations.)

Introduce `deprecatedConvertClientDBThreadInfoToRawThreadInfo` which turns a ClientDB representation of `RawThreadInfo` into `LegacyRawThreadInfo`. The reason for this function, as described in D10198, is to maintain correctness of existing Redux migrations. (As an aside, Redux migrations would be a great thing to write unit tests for because often our assumptions about "current state of the codebase" when modifying helper functions don't apply to migrations and can break them. I just happened to notice `convertClientDBThreadInfoToRawThreadInfo` when looking at creating a new Redux migration and realized this would break old migrations.) --- Depends on D10209

Introduce `deprecatedConvertClientDBThreadInfoToRawThreadInfo` which turns a ClientDB representation of `RawThreadInfo` into `LegacyRawThreadInfo`. The reason for this function, as described in D10198, is to maintain correctness of existing Redux migrations. (As an aside, Redux migrations would be a great thing to write unit tests for because often our assumptions about "current state of the codebase" when modifying helper functions don't apply to migrations and can break them. I just happened to notice `convertClientDBThreadInfoToRawThreadInfo` when looking at creating a new Redux migration and realized this would break old migrations.) --- Depends on D10209