ComponentsConfiguration

These values are safe defaults and should not require manual changes.

This class hosts all the config parameters that the ComponentTree configures it self .... enable and disable features ... A Component tree uses the .defaultComponentsConfiguration by default but a Builder can be used to create new instances of the config to override the default parameters ... The default config values can also be overridden by manually setting their values in .defaultBuilder

Types

Link copied to clipboard
class Builder

This is a builder that only exists so that Java clients can have an easier time creating and overriding specific configurations. For Kotlin one can use directly the named parameters on the ComponentsConfiguration constructor.

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

Determines whether we log, crash, or do nothing if an invalid com.facebook.litho.ComponentHost view modification is detected.

Link copied to clipboard

If enabled, this will enable the recycling of com.facebook.litho.ComponentHost using MountItemsPool

Link copied to clipboard
Link copied to clipboard

You can define a ComponentTreeDebugEventListener to listen on specific litho lifecycle related events.

Link copied to clipboard
Link copied to clipboard
Link copied to clipboard

Controls whether we attempt to batch state updates to avoid running the render process for every state update in a small time window. This has been proven to be an overall improvement for performance so it's highly advised to not disable it.

Link copied to clipboard

This class is an error event handler that clients can optionally set on a ComponentTree to gracefully handle uncaught/unhandled exceptions thrown from the framework while resolving a layout.

Link copied to clipboard

Whether the com.facebook.rendercore.MountState can be mounted using incremental mount.

Link copied to clipboard

Whether the ComponentTree should be using State Reconciliation.

Link copied to clipboard
Link copied to clipboard

The handler ComponentTree will be used to run the pre-allocation process

Link copied to clipboard

Whether we use a Recycler based on a Primitive implementation.

Link copied to clipboard

We have detected a scenario where we don't process visibility bounds change if the localVisibleRect goes of the viewport and a LithoView is nested on an Host that is still visible.

Link copied to clipboard

This determines if the ComponentTree attached to this configuration, will attempt to detect and ignore duplicate state updates coming from usages in the Specs API.

Link copied to clipboard

LithoViewAttributesExtension is an extension for LithoView that allows setting custom view attributes on the underlying Android View or Drawable. This extension plays a crucial role when working with Litho components because it enables the modification of view properties not already exposed by the Litho framework. The proper functioning of this extension is vital for maintaining correct component behavior during mount and unmount processes, especially when controlled by animations.

Link copied to clipboard
Link copied to clipboard

Whether the com.facebook.LithoView associated with the com.facebook.litho.ComponentTree will process visibility events.