Update jest config to ignore Gridstack for transformation steps

Robert Huntrequested to merge
add-gridstack-transform-ignore-for-gitlab-ui-jest into main

What does this MR do?

This MR adds the Gridstack library as an exclusion to this repo's jest transformation config. This is to fix integration with Add dashboard grid internal component for use w... (gitlab-org/gitlab-services/design.gitlab.com!4555 - merged). See https://gitlab.com/gitlab-org/duo-ui/-/jobs/10402124026 for an example failure.

I believe that the reason this is having issues is that we're mocking @gitlab/ui but requiring the actual package too: https://gitlab.com/gitlab-org/duo-ui/blob/3bad011501d4a4f50670ee72aeed95c555f146bc/__mocks__/@gitlab/ui.js#L6-6

Screenshots or screen recordings

N/A

How to set up and validate locally

You can't test Gridstack in this MR, as it isn't used. However, if you'd like to see if in action, see:

Integration merge requests

No integration on this side, but will help with work on:

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • [-] If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • [-] If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • [-] If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • [-] Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • [-] All actions and functionality can be done with a keyboard.
  • [-] Links, buttons, and controls have a visible focus state.
  • [-] All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • [-] Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • [-] Color combinations have sufficient contrast.
Edited by Robert Hunt

Merge request reports