react-lua-freeze

KO | EN

gitlite — search

#javascript #golang #android #rust #deep-learning #linux #docker #java #windows #awesome #awesome-list #security #openai #open-source

react-lua-freeze

(★ 16)

🧊 Prevent React component subtrees from rendering.

react-lua-freeze 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# `🧊 React Freeze`

**Prevent React component subtrees from rendering.**

</div>

## What is this?

This library lets you freeze the renders of parts of the React component tree using `Suspense` mechanism introduced in React 17.
The main use case of this library is to avoid unnecessary re-renders of parts of the app that are not visible to the user at a given moment.
The frozen components **are not unmounted** when they are replaced with a placeholder view, so their React state and corresponding Roblox Instances are retained during the freeze, keeping things like scroll position and input state unchanged.

With `react-freeze`, we are able to suspend renders for the hidden screens and, as a result, save React from doing unnecessary computation (such as reconciliation, sending view change updates, etc.).

This Luau library is ported from Software Mansion's [`react-freeze`](https://github.com/software-mansion/react-freeze).

## Quick Start

Wrap some components you want to freeze and pass `freeze` option to control whether renders in that components should be suspended:

```luau
local function SomeComponent(props: { shouldSuspendRendering: boolean })
    return e(Freeze, {
        freeze = props.shouldSuspendRendering
    }, {
        MyOtherComponent = e(MyOtherComponent),
    })
end
```

## Component Docs

The `react-freeze` library exports a single component called `<Freeze>`.
It can be used as a boundary for components for which we want to suspend rendering.
This takes the following options:

### `freeze: boolean`

This options can be used to control whether components rendered under `Freeze` should or should not re-render.
If set to `true`, all renders for components from the `Freeze` subtree will be suspended until the prop changes to `false`.

### `placeholder: React.ReactNode?`

This parameter can be used to customize what the `Freeze` component should render when it is in the frozen state (`freeze = true`).
This is an optional parameter and by default it renders a Fragment (aka nothing).
Note, that it is best to "freeze" only components that are not visible to the user at given moment, so in general customizing this should not be necessary.
However, if replacing frozen views with just a Fragment can break layout of you app, you can use this parameter to show a placeholder that will keep all non-frozen parts of your application in the same place.

## FAQ

## When the component subtree is frozen, what happens to state changes that are executed on that subtree

All state changes are executed as usual, they just won't trigger a render of the updated component until the component comes back from the frozen state.

## What happens to the non-React state of the component after defrost? Like for example scroll position?

Since all the Roblox Instances are kept when the component is frozen, their state (such as scroll position, text typed into text input fields, etc.) is restored when they come back from the frozen state.

## What happens when there is an update in a Rodux store that the frozen component is subscribed to?

Rodux and other state-management solutions rely on manually triggering re-renders for components that they want to update when the store state changes.
When component is frozen it won't render even when Rodux requests it, however methods such as `mapStateToProps` or selectors provided to `useSelector` will still run on store updates.
After the component comes back from frozen state, it will render and pick up the most up-to-date data from the store.

## Can freezing some of my app components break my app? And how?

There are few ways `<Freeze>` can alter the app behavior:

1. When attempting to freeze parts of the app that is visible to the user at a given moment -- in this case the frozen part is going to be replaced by the placeholder (or just by nothing if no placeholder is provided). So unless you really want this behavior make sure to only set `freeze` to `true` when the given subtree should not be visible and you expect the user to not interact with it. A good example are screens on the navigation stack that are down the stack hierarchy when you push more content.
2. When you rely on the frozen parts of the layout to properly position the unfrozen parts. Note that when a component is in a frozen state it gets replaced by a placeholder (or by nothing if you don't provide one). This may impact the layout of the rest of your application. This can be workaround by making the placeholder take the same amount of space as the view it replaces, or by only freezing parts that are positioned absolutely (e.g. the component that takes up the whole screen).
3. When the component render method has side-effects that relay on running for all prop/state updates. Typically, performing side-effects in render is undesirable when writing React code but it can happen in your codebase nonetheless. Note that when the subtree is frozen your component may not be rendered for all the state updates and render method won't execute for some of the changes that happen during that phase. However, when the component gets back from the frozen state it will render with the most up-to-date version of the state, and if that suffice for the side-effect logic to be correct you should be ok.

react-lua-freeze

react-lua-freeze 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

react-lua-freeze

react-lua-freeze 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README