antd-crud-table API
    Preparing search index...

    Interface OperationsStrategy<T, K>

    Serves records through consumer-supplied operations.

    interface OperationsStrategy<T, K extends keyof T> {
        defaultPageSize?: number;
        generateId?: IdGenerator<T, K>;
        locale?: Partial<CrudTableLocale>;
        notifications?: boolean;
        onError?: (operation: CrudOperationName, error: Error) => void;
        onSuccess?: (operation: CrudOperationName, payload: unknown) => void;
        operations: CrudOperations<T, K>;
        optimisticUpdates?: boolean;
        refreshAfterMutation?: boolean;
    }

    Type Parameters

    • T
    • K extends keyof T

    Hierarchy

    • UseCrudTableOptionsBase<T, K>
      • OperationsStrategy
    Index
    defaultPageSize? generateId? locale? notifications? onError? onSuccess? operations optimisticUpdates? refreshAfterMutation?
    defaultPageSize?: number

    Rows per page for the hook's own reads. Defaults to 10.

    generateId?: IdGenerator<T, K>

    Replaces the built-in identity policy for the in-memory strategies.

    locale?: Partial<CrudTableLocale>

    Overrides for the toast wording.

    CrudTable passes its own resolved locale down, so this is only needed when the hook is used on its own.

    notifications?: boolean

    Show antd toasts for the outcome of each operation.

    onError?: (operation: CrudOperationName, error: Error) => void

    Called when an operation fails, with a real Error rather than the raw throw.

    onSuccess?: (operation: CrudOperationName, payload: unknown) => void

    Called after an operation succeeds, with whatever it produced.

    operations: CrudOperations<T, K>

    Your own implementations. Omitted operations fail with a named error.

    optimisticUpdates?: boolean

    Apply mutations to local state immediately instead of re-reading.

    Trades consistency for responsiveness: server-assigned fields will not be reflected until the next list.

    refreshAfterMutation?: boolean

    Re-read the list after a successful mutation.

    Defaults to true for standalone hook consumers, which render from state.data. CrudTable sets it false: it renders from ProTable's own request pipeline and reloads through actionRef, so leaving this on issued two list requests for every write.

    Settings
    Member Visibility

    On This Page
    Properties