Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Feature request: a framework render slot for axis tick labels

Abierto
  • ¿Algo no está bien?
#181 1 comentario 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
data-visualization

Línea de trabajo

Start by reading the axis tick configuration under scales.y and the existing tooltip render path, RendererChart from @tanstack/charts/react/tooltip. The issue suggests either an axis render slot or exposing resolved tick positions and the plot rect, so the API and layout behavior still need design. Done means framework-rendered tick labels can be positioned and sized by the chart without duplicating plot layout math.

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

Descripción

Version: @tanstack/charts 1.0.0, React adapter

Problem

Tick labels are SVG text. ticks.format returns a string. There is no way to render a framework component (an icon, an image, a styled badge) as a tick label.

Recharts lets you pass a component as tick. We used this for an Elo chart. Each y tick shows a skill level icon and the Elo value next to it. Each x tick on one variant shows a styled match result marker.

The tooltip already has a framework render path (RendererChart from @tanstack/charts/react/tooltip). Tick labels do not.

Our workaround

We hide the axis labels in the chart and render them as HTML over the plot. The component must know the plot layout:

  • the y position of each tick, as a fraction of the y domain
  • the x position of each tick, as a fraction of the x domain
  • the plot insets and the x padding, so that the HTML labels line up with the SVG plot

Simplified from our code:

// Our own copy of the plot insets (example values). It must match the
// chart definition.
const layout = { top: 8, bottom: 24, start: 72, end: 8, xPadding: 12 };

<Frame>
  <Chart definition={definition} ariaLabel={label} height={height} />

  <YAxisLayer
    style={{
      insetBlock: `${layout.top}px ${layout.bottom}px`,
      inlineSize: layout.start - TICK_GAP,
    }}
  >
    {yTicks.map(tick => (
      <SkillTick key={tick} value={tick} offset={getYFraction(yDomain, tick)} />
    ))}
  </YAxisLayer>

  <PlotLayer
    style={{
      insetBlock: `${layout.top}px ${layout.bottom}px`,
      insetInline: `${layout.start + layout.xPadding}px ${layout.end + layout.xPadding}px`,
    }}
  >
    {rows.map(row => (
      <ResultTick key={row.x} row={row} position={getXFraction(xDomain, row.x)} />
    ))}
  </PlotLayer>
</Frame>

This works, but:

  • We copy the scale math and the plot insets into the component. If the library changes its layout, the labels move away from the plot.
  • The library cannot measure the labels, so we reserve the label space by hand (a fixed gap and a fixed width).
  • The labels are not part of the chart accessibility tree.

Suggested API

A render slot on the axis, for the adapters that support it. For example:

scales: {
  y: {
    scale: scaleLinear,
    axis: {
      ticks: {
        render: tick => <SkillTick value={tick.value} />,
        // the space the library reserves for each label
        size: { width: 64, height: 24 },
      },
    },
  },
},

The library positions each slot at the tick, like it does for the tooltip. An alternative is to expose the resolved tick positions and the plot rect to the framework layer (for example through a callback or a hook), so that an overlay does not have to copy the math.

Written by an agent (Claude Code, claude-opus-5-5).

Lenguaje dominante
TypeScript
Estrellas
842
Forks
53
Merge medio
4 h 40 min
PR fusionados (30 d)
16

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 TanStack/charts

Todos los issues de TanStack/charts

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.