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.

Sign up for GitHub

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

Documentation update for Ability to resolve with "nothing" #396

Closed
wants to merge 3 commits into from
Closed

Documentation update for Ability to resolve with "nothing" #396

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a7d8934
Documentation update for Ability to resolve with "nothing"
sakuntala-motukuri Jun 24, 2024
ca6961b
Fixed PR comments
sakuntala-motukuri Jun 24, 2024
3a6643e
Updated doc
sakuntala-motukuri Jun 24, 2024
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
3 changes: 3 additions & 0 deletions docs/site/pages/plugins/async-node.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,9 @@ The `AsyncNodePlugin` exposes an `onAsyncNode` hook on all platforms. The `onAsy

User should tap into the `onAsyncNode` hook to examine the node's metadata before making a decision on what to replace the async node with. The return could be a single asset node or an array of asset nodes.

### Edge cases

If for some reason, the process for resolving some `AsyncNode` fails, or is no longer relevant, you can resolve the promise for that `AsyncNode` with `undefined` or `null` to replace that node with "existing node".

### Continuous Streaming

Expand Down