[🐛 Bug]: Typescript support for Custom matchers seems broken with V9 · webdriverio/webdriverio#13387

(2 评论) (0 反应) (0 负责人)JavaScript (6,029 star) (1,793 fork)batch import

Bug 🐛help wanted

描述

Have you read the Contributing Guidelines on issues?

I have read the Contributing Guidelines on issues.

WebdriverIO Version

Node.js Version

Mode

WDIO Testrunner

Which capabilities are you using?

No response

What happened?

When creating a new customer matcher and you want to use ExpectWebdriverIO.PartialMatcher you get a TS error Namespace 'global.ExpectWebdriverIO' has no exported member 'PartialMatcher'. This prevents the Visual Testing Service to upgrade to V9 without using a workaround. See also https://github.com/webdriverio/visual-testing/actions/runs/10442443274/job/28914748091?pr=417

What is your expected behavior?

No response

How to reproduce the bug.

Clone the Visual project and use this PR

Relevant log output

Namespace 'global.ExpectWebdriverIO' has no exported member 'PartialMatcher'

Code of Conduct

I agree to follow this project's Code of Conduct

Is there an existing issue for this?

I have searched the existing issues

贡献者指南

技术栈: typescriptnodejs
领域: testing
议题类型: bug
难度: 4
预计时间: 1-3 hours
活动状态: active
清晰度: clear
前置要求: TypeScript knowledgeUnderstanding of WebdriverIO custom matchers
新手友好度: 30
研究方向: Investigate the type definitions in the @wdio/expect package. The error indicates that `PartialMatcher` is not exported from the `ExpectWebdriverIO` namespace. Check the linked PR (webdriverio/visual testing#417) for reproduction steps. Look into the type declaration files in the repository, especially those related to expect and matchers, to find where the export should be added.