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

Clone not working with a TabbedForm on the Create component

Abierto
  • ¿Algo no está bien?
#10,678 3 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
react, typescript
Área
frontend

Línea de trabajo

Comienza con el repositorio de reproducción ra-tabbedform-clone, especialmente con CloneStateButton y el componente PostCreate que usa TabbedForm, y compara su comportamiento con la configuración más reciente de react-admin descrita en el issue. Reproduce el flujo de clonación editando el título, cambiando de General a Misc y volviendo, y verifica después que las ediciones se conserven al regresar a la primera pestaña.

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

Descripción

needs more info v4

What you were expecting:

When cloning a resource, a tabbed create form shows all the values from the original record (except the omitted id). And when changes the values in that create form, the changes are kept even when switching tabs.

What happened instead:

The create form looks ok, it shows the values of the cloned record. However when changing prefilled values on tab 1 and navigate to tab 2. When you go back to tab 1, the changes are gone.

Steps to reproduce:

  • Go to posts resource
  • Click on a post
  • Click "Clone" button
  • Fill in the "id" field (which is empty because omitted in the clone)
  • Change the "title" (which was prefilled with value of cloned record)
  • Switch to second tab "Misc" of the create form by clicking on that tab
  • Go back to first tab "General" by clicking on that tab
  • Note that "id" is still filled in
  • Note that "title" changes are gone... it is back to it's original value of the cloned record. ==> bug
  • Change the "title" again
  • Switch to second tab and back to first tab again
  • Note that this second time the "title" changes are still there

Related code:

  • Started from the basic react-admin app via npx [email protected] ra-tabbedform-clone
  • Added a CloneStateButton to clone via location.state instead of via search
  • Made a simple PostEdit component
  • Made a simple PostCreate component that uses TabbedForm

Other information:

Only related issue I found is from the v3 version: https://github.com/marmelab/react-admin/issues/4066

Tried to reproduce this on latest react-admin v5.7.2 via npx create-react-admin@latest ra-tabbedform-latest --data-provider fakerest --resource posts. But there it seems to work.

Using the regular CloneButton this problem does not occur. However, that uses the location search and I do not want my complete record state in the URL. The docs state "In general, using the location state is a safe bet."

Environment

  • React-admin version: 4.16.20
  • Last version that did not exhibit the issue (if applicable):
  • React version: 18.3.1
  • Browser: Chrome Version 131.0.6778.265 (Official Build) (64-bit)
  • Stack trace (in case of a JS error):
Lenguaje dominante
TypeScript
Estrellas
27k
Forks
5.5k
Merge medio
1 d 3 min
PR fusionados (30 d)
32

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 marmelab/react-admin

Todos los issues de marmelab/react-admin

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.