@fasal26: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Hello @fasal26,

Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Enterprise tests are not yet completed. You need to wait until Enterprise CI/docker-image status check is successful, before triggering E2E tests.

Apart of the linting issues, look good to me.

@larkox
linting issues resolved

Some of the issues have been resolved, but the linter that you used reorganized the imports in a way that don't match our linting rules. Would you mind fixing those as well?

ESLint should be able to fix those automatically if you run npm run fix

Some of the issues have been resolved, but the linter that you used reorganized the imports in a way that don't match our linting rules. Would you mind fixing those as well?

ESLint should be able to fix those automatically if you run npm run fix

Resolved

/e2e-tests

E2E test triggered successfully for PR #26957. The corresponding commit's status check will be available shortly.

E2E test run is starting for commit 1a32d3c41a5a6ffa884c542c4750b34c244e339d.
You can check its progress by either:

• Looking at the corresponding commit status, which will be available in a few moments: E2E Tests/test.
• Looking at the E2E test's Workflow Run, with Run ID 9205447242.
• Looking at the E2E test's Cycle on the Automation Dashboard.

Test server destroyed