Skip to content

Refactor form data structure and keys - #1

Open
Ulimonster wants to merge 5 commits into
mainfrom
english
Open

Refactor form data structure and keys#1
Ulimonster wants to merge 5 commits into
mainfrom
english

Conversation

@Ulimonster

Copy link
Copy Markdown
Owner

Update getFormData in generador_prompt.html to a reorganized, English-keyed object shape. Consolidates rol_sistema and tipo_salida into instruction_config (adds persona, framework, temperature, style, standard), renames contexto_curricular -> curriculum_context, planeacion -> planning (with renamed subfields), tareas -> tasks, and refinamiento -> reasoning_phase. Preserves original default values/behaviour while standardizing property names and adding instruction metadata.

Update getFormData in generador_prompt.html to a reorganized, English-keyed object shape. Consolidates rol_sistema and tipo_salida into instruction_config (adds persona, framework, temperature, style, standard), renames contexto_curricular -> curriculum_context, planeacion -> planning (with renamed subfields), tareas -> tasks, and refinamiento -> reasoning_phase. Preserves original default values/behaviour while standardizing property names and adding instruction metadata.
Update generador_prompt.html to embed the `campo` variable into the generated JSON filename. The download filename now uses `Prompt_NEM_F6_${campo}${date}.json` instead of a static prefix, making saved files distinguishable by campo and date.
Change the form validation to check the English-named JSON field (data.curriculum_context.formative_field) instead of the original Spanish key (data.contexto_curricular.campo_formativo). Added a brief inline comment about basic JSON field validation; preserves the existing alert when the field is missing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant