VAMC system/facilities selectors, connectors, and tests

[eselkin]

Summary

• Selectors, Connectors, and tests for KISS data from Drupal View in content-build
• Sitewide Facilities

Related issue(s)

• Get Drupal View of System Ids and Connected Facility Ids into KISS format  va.gov-cms#16019

Testing done

• Adds testing for preprocess and selectors
• Checked unit tests
• No possibility for e2e test yet until something implements the selectors/connectors

Screenshots

N/A

What areas of the site does it impact?

Added new selectors/connectors/preprocessors for KISS data, no existing site functionality changed.

Acceptance criteria

• Selector is created in vets-website
• Connector is creates in vets-website

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 (No updated docs)
• Screenshot of the developed feature is added (n/a)
• Accessibility testing has been performed (n/a)

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 (n/a)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user (No routes or components changed)

Requested Feedback

Check that tests (unit) are passing.
Can verify other content-build PR functions here

[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.

[maxx1128]

This checks out for me, and I also learned the term "tuples." 😃