component-shape-gpui-macros 0.3.2

mod derives;

use proc_macro::TokenStream;

/// Derive macro for GPUI component shape metadata.
///
/// When `#[gpui_component_shape(...)]` is present, `state = ...` may be omitted
/// if the backing state follows the `ComponentState` naming convention. By
/// default the derive calls `<State>::new(window, cx)`. Override the constructor
/// with `new = ...`, a closure, or a direct constructor expression.
///
/// `value = ...` or `values(...)` publish exact supported value types. For
/// `value_binding` shapes, value compatibility may also be inferred from
/// `State: GpuiComponentStateValueBinding<T>`.
///
/// Common MCP input metadata is inferred from declared value metadata when the
/// shape has unambiguous string, boolean, numeric, date, date-time, array, set,
/// range, object-map, or unconstrained JSON value shapes. Each generated
/// `ComponentShapeFor<Value>` impl carries the value-specific metadata; the
/// shape-level metadata is emitted only when all declared values agree. Use
/// `mcp_input = string`, `mcp_input = object`, or another `McpInput` expression
/// when a generic or custom shape knows its model-facing MCP input better than
/// the value type can be inferred.
#[proc_macro_derive(GpuiComponentShape, attributes(gpui_component_shape))]
pub fn derive_gpui_component_shape(input: TokenStream) -> TokenStream {
    derives::component_shape_state::from(input)
}

/// Function-like macro for declaring a local GPUI component shape around
/// external component/state types.
///
/// The backing state may be declared as `type State = ...;` or `state = ...;`.
/// When no explicit `value = ...` or `values(...)` metadata is present, a
/// nested `GpuiComponentValueBinding<T>` impl publishes `T` as a supported value
/// and enables value-binding metadata.
///
/// Common MCP input metadata is inferred from declared value metadata when the
/// shape has unambiguous string, boolean, numeric, date, date-time, array, set,
/// range, object-map, or unconstrained JSON value shapes. Each generated
/// `ComponentShapeFor<Value>` impl carries the value-specific metadata; the
/// shape-level metadata is emitted only when all declared values agree. Use
/// `mcp_input = string`, `mcp_input = object`, or another `McpInput` expression
/// when a generic or custom shape knows its model-facing MCP input better than
/// the value type can be inferred.
#[proc_macro]
pub fn component_shape(input: TokenStream) -> TokenStream {
    derives::component_shape::function(input)
}