Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codemod act -> await act (1/?) #26334

Merged
merged 1 commit into from
Mar 7, 2023
Merged

Commits on Mar 7, 2023

  1. Codemod act -> await act (1/?)

    Similar to the rationale for `waitFor` (see facebook#26285), we should always
    await the result of an `act` call so that microtasks have a chance
    to fire.
    
    This only affects the internal `act` that we use in our repo, for now.
    In the public `act` API, we don't yet require this; however, we
    effectively will for any update that triggers suspense once `use` lands.
    So we likely will start warning in an upcoming minor.
    acdlite committed Mar 7, 2023
    Configuration menu
    Copy the full SHA
    2205d45 View commit details
    Browse the repository at this point in the history