VATEAM-101161: Normalize Custom Step with pages and components

[derekhouck]

Are you removing or changing a registry.json entryName in this PR?

• No, I'm not changing any entryNames (skip to Summary and delete the rest of this section)
• Yes, I'm removing or changing an entryName

Summary

• Updates the GraphQL query to fetch the proper fields for Custom Step Paragraph entities.
• Normalizes fields for Custom Steps as well as their pages and the Text Input component.

Example output

      {
        "id": 172736,
        "type": "digital_form_custom_step",
        "chapterTitle": "My custom step",
        "pages": [
          {
            "bodyText": "My custom body text",
            "components": [
              {
                "hint": "This is optional hint text",
                "label": "My custom text input",
                "required": true,
                "type": "digital_form_text_input"
              }
            ],
            "pageTitle": "My custom page"
          },
          {
            "bodyText": "With additonal body text",
            "components": [
              {
                "hint": null,
                "label": "A text input with no hint text",
                "required": true,
                "type": "digital_form_text_input"
              },
              {
                "hint": "This text input is not required",
                "label": "An optional text input",
                "required": false,
                "type": "digital_form_text_input"
              }
            ],
            "pageTitle": "An additional page"
          }
        ]
      }

Related issue(s)

• Normalize custom step (with text input) in content-build va.gov-team#101161

Testing done

• New/updated unit tests for the new and updated GraphQL fragments and the Digital Form post processor
• Pulled local Drupal data and confirmed the resulting output from content-build

What areas of the site does it impact?

Only affects the output of digital-forms.json.

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[va-vfs-bot]

ESLint is disabled

vets-website uses ESLint to help enforce code quality. In most situations we would like ESLint to remain enabled.

What you can do

See if the code can be refactored to avoid disabling ESLint, or wait for a VSP review.

[derekhouck]

To avoid overloading postProcessDigitalForm.js, I've moved all code relating to chapters to this page.

[derekhouck]

There are no changes to extractAdditionalFields

[derekhouck]

This switch statement is ripe for a refactor, but it will make more sense to do that when I add custom List & Loops at a later date.

[derekhouck]

These methods were moved out of postProcessDigitalForm.js to give that file more focus. No changes were made to either method.