Skip to content

Screen transitions trigger an excessive number of react commits #28158

Description

@muttmuure

Coming from here: https://expensify.slack.com/archives/C05LX9D6E07/p1694783353289039

Problem

A number of screen transitions (we mainly looked at screens related to workspaces) trigger an excessive number of react commits.

In some scenarios we are seeing hundreds of commits (250+).The majority of these commits are due to subscriptions to onyx.

Solution

We should aim at having juts a few commits when a screen is being pushed (ideally just one commit).

Updates for components rendered in a single batch should also be triggered in a single batch and committed with a single commit.

Figure out how to extend Expensify/react-native-onyx#315 to web.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions