Skip to content

Edit for <Iterate>'s docs #13

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

Merged
merged 3 commits into from
Dec 24, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/Iterate/index.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -38,11 +38,11 @@ export { Iterate, type IterateProps };
* }
* ```
*
* `<Iterate>` may be preferable over {@link useAsyncIter `useAsyncIter`} typically as the UI area it
* controls the rendering for is constrainable down to the essential, saving some React elements from
* unnecessary re-renderings while placable clearly and elegantly within some larger component's UI
* output. In regard to {@link useAsyncIter `useAsyncIter`} being a hook though, it has to
* re-render the entire component output for every new value.
* `<Iterate>` may be preferable over {@link useAsyncIter `useAsyncIter`} typically as the UI area
* it re-renders can be expressively confined to the minimum necessary, saving unrelated elements
* within UI of a larger component from re-evaluating. On the other hand, the
* counterpart {@link useAsyncIter `useAsyncIter`} being a hook has to re-render the entire
* component output for every new value.
*
* Given an async iterable as the `value` prop, this component will iterate it and render each new
* value that becomes available together with any possible completion or error it may run into.
Expand Down
Loading