sif-dialog-migration

Port ListAndDialog components from v1/Formik to v2/RHF using ModalFormAndList.

2|Updated Jun 3, 2022
One-click install
npx skills add https://github.com/navikt/sif-brukerdialog --skill sif-dialog-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sif-dialog-migration
Source: https://github.com/navikt/sif-brukerdialog/tree/main/.github/skills/sif-dialog-migration
Command: npx skills add https://github.com/navikt/sif-brukerdialog --skill sif-dialog-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This migration skill addresses the workload of porting ListAndDialog components from sif-common-forms-ds v1/Formik to sif-soknad-forms v2/RHF using a standardized ModalFormAndList pattern, reducing time and risk during upgrades.

Core Features & Use Cases

  • Port a single dialog at a time, including XxxDialogForm, XxxDialog, XxxList, and XxxListAndDialog wrappers.
  • Create i18n, story, and exports for v2 components, following the migration checklist.
  • Use when a user requests porting of a specific v1 dialog to v2, or when porting an entire set of dialogs in a controlled way.

Quick Start

Begin by identifying the v1 dialogs to port, then implement the v2 domain types and wrappers following the migration steps.

Frequently Asked Questions about sif-dialog-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Formik dialogs to RHF using ModalFormAndList?

You can migrate Formik dialogs to RHF by porting ListAndDialog components from sif-common-forms-ds v1 to sif-soknad-forms v2 using the ModalFormAndList pattern. This process involves creating domain types, forms, lists, and i18n wrappers for the v2 components.

What is the process for porting a single dialog from sif-common-forms-ds to sif-soknad-forms?

Porting a single dialog involves migrating XxxDialogForm, XxxDialog, XxxList, and XxxListAndDialog wrappers. You must implement v2 domain types, validate forms, and verify content parity before finalizing the migration.

How do I ensure content parity when migrating v1 dialogs to v2?

Ensure content parity during dialog migration by running get_errors checks and following the publication workflows. This verifies that the v2 RHF components accurately replicate the validation and behavior of the v1 Formik components.

Can I migrate an entire set of ListAndDialog dialogs at once?

Yes, you can migrate an entire set of ListAndDialog dialogs in a controlled way. The migration covers applying domain types, forms, lists, stories, and i18n collectively, ensuring all v2 components are wired for exports.