dioxus_core

Module prelude

Source
Expand description

The purpose of this module is to alleviate imports of many common types

This includes types like Element, and Component.

Re-exports§

  • pub use crate::innerlude::AnyValue;
  • pub use crate::innerlude::OptionStringFromMarker;
  • pub use crate::innerlude::SuspenseBoundary;
  • pub use crate::innerlude::SuspenseBoundary;

Structs§

  • An attribute on a DOM node, such as id="my-thing" or href="https://example.com"
  • The callback type generated by the rsx! macro when an on field is specified for components.
  • A context with information about suspended components
  • A wrapper around some generic data that handles the event’s state
  • Reactivity
  • A global runtime that is shared across all scopes that provides the async runtime and context API
  • A guard for a new runtime. This must be used to override the current runtime when importing components from a dynamic library that has it’s own runtime.
  • A component’s unique identifier.
  • A component’s rendered state.
  • A task that has been suspended which may have an optional loading placeholder
  • Properties for the SuspenseBoundary() component.
  • A context with information about suspended components
  • A task’s unique identifier.
  • A static layout of a UI tree that describes a set of dynamic and static nodes.
  • A reference to a template along with any context needed to hydrate it
  • A reference to a template along with any context needed to hydrate it
  • A virtual node system that progresses user events and diffs UI trees.

Enums§

Traits§

  • Any component that implements the ComponentFn trait can be used as a component.
  • Provides context methods to Result and Option types that are compatible with CapturedError
  • A trait for anything that has a dynamic list of attributes
  • A value that can be converted into an attribute value
  • A trait that allows various items to be converted into a dynamic node for the rsx macro
  • Every “Props” used for a component must implement the Properties trait. This trait gives some hints to Dioxus on how to memoize the props and some additional optimizations that can be made. We strongly encourage using the derive macro to implement the Properties trait automatically.
  • A enhanced version of the From trait that allows with more flexibility.
  • A enhanced version of the Into trait that allows with more flexibility.
  • Provides context methods to Result<T, RenderError> to show loading indicators for suspended results

Functions§

  • Create a new error boundary component that catches any errors thrown from child components
  • Create inline fragments using Component syntax.
  • Suspense Boundaries let you render a fallback UI while a child component is suspended.
  • Consume context from the current scope
  • Consume context from the current scope
  • Returns the current owner. This owner will be used to drop any Copy state that is created by the generational-box crate.
  • Get the current scope id
  • This utility function launches the builder method so rsx! and html! macros can use the typed-builder pattern to initialize a component’s props.
  • Get the current render since the inception of this component
  • Check if the current scope has a context
  • Mark the current scope as dirty, causing it to re-render
  • Mark the current scope as dirty, causing it to re-render
  • Get the parent of the current scope if it exists
  • Provide context to the current scope
  • Provide an error boundary to catch errors from child components
  • Provide a context to the root scope
  • Queue an effect to run after the next render. You generally shouldn’t need to interact with this function directly. use_effect will call this function for you.
  • Informs the scheduler that this task is no longer needed and should be removed.
  • Schedule an update for the current component
  • Schedule an update for any component given its ScopeId.
  • Spawns the future but does not return the Task. This task will automatically be canceled when the component is dropped.
  • Spawn a future that Dioxus won’t clean up when this component is unmounted
  • Start a new future on the same thread as the rest of the VirtualDom.
  • Suspended the current component on a specific task and then return None
  • Throw a CapturedError into the current scope. The error will bubble up to the nearest crate::prelude::ErrorBoundary() or the root of the app.
  • Consume context from the current scope
  • Push this function to be run after the next render
  • A hook that allows you to insert a “before render” function.
  • Creates a callback that will be run before the component is removed. This can be used to clean up side effects from the component (created with use_effect).
  • Store a value between renders. The foundational hook for all other hooks.
  • Use a hook with a cleanup function
  • Run a closure with the given owner.

Type Aliases§