[Table] Context from a wrapper around Column is lost when the column header renders

Abierto
  • ¿Algo no está bien?
#10,632 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
frontend

Línea de trabajo

Start with the minimal Table/Column reproduction using react-aria-components 1.21.1, @tanstack/react-table 9.2.4, and React 19.3.0, then trace how RAC collects and renders Column header content. Confirm the failure of useHeaderContext() and investigate whether the provider can remain available or whether a renderer API is needed. Done means the header context works through Column rendering, or a documented way exists to pass the collected header instance explicitly.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Description

I am integrating TanStack Table v9's createTableHook with React Aria Components Table. TanStack’s hook factory can register header components that use a context hook such as useHeaderContext() to access the current TanStack header's state.

This works when the registered component is rendered in the normal React tree. It fails when used as the content of a React Aria Column: RAC collects the column definitions and renders their header content through its collection machinery, outside the wrapper’s context provider.

This seems related to #7049: “Context set in collection item node not propagating”, which describes the same general context-propagation problem. This report is a concrete Table/Column integration case.

Minimal example

A simplified TanStack hook registers a component that reads the current header from context:

const { useAppTable, useHeaderContext } = createTableHook({
  features,
  headerComponents: {
    SortableHeader: () => {
      const header = useHeaderContext();

      return (
        <Column
          id={header.id}
          allowsSorting={header.column.getCanSort()}
        >
          <FlexRender header={header} />
        </Column>
      );
    },
  },
});

The app wraps that component in TanStack’s header provider:

<table.AppTable>
  <Table>
    <TableHeader>
      {headers.map((header) => (
        <table.AppHeader header={header} key={header.id}>
          {(appHeader) => <appHeader.SortableHeader />}
        </table.AppHeader>
      ))}
    </TableHeader>
    {/* rows */}
  </Table>
</table.AppTable>

At runtime, useHeaderContext() throws:

useHeaderContext must be used within an AppHeader or AppFooter component.

Passing the header explicitly instead of reading it from context works around the problem:

<Column id={header.id} allowsSorting={header.column.getCanSort()}>
  <FlexRender header={header} />
</Column>

Expected behavior

A React context provider around a Column’s rendered header content would remain available to that content, or RAC would provide an API for passing the collected column/header instance to the renderer without relying on context.

Actual behavior

The provider appears to wrap the JSX returned for the column, but the content rendered by RAC’s collection-based table header does not receive that context.

Environment

  • react-aria-components: 1.21.1
  • @tanstack/react-table: 9.2.4
  • React: 19.3.0
Lenguaje dominante
TypeScript
Estrellas
16k
Forks
1.6k
Merge medio
3 d 9 h
PR fusionados (30 d)
45

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de adobe/react-spectrum

Todos los issues de adobe/react-spectrum

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.