fixed minor TS typing issues in class Result and output.result

[danielrentz]

Motivation/Description of the PR

Two small fixes for Typescript typings:

• the function output.result misses a declaration for the optional parameter "failedHooks".
• the "failures" in class Result may contain numbers or strings. The exact type for a single failure report is [string, number, string, string, string] but that is not possible to declare with vanilla JSDoc. Added typedef Failure as string/number array, and replaced string[] with the new type.

Unrelated changes in plugins.md have been auto-generated by npm run docs.

Applicable helpers:

• Playwright
• Puppeteer
• WebDriver
• REST
• FileHelper
• Appium
• TestCafe

Applicable plugins:

• allure
• autoDelay
• autoLogin
• customLocator
• pauseOnFail
• coverage
• retryFailedStep
• screenshotOnFail
• selenoid
• stepByStepReport
• stepTimeout
• wdio
• subtitles

Type of change

• 🔥 Breaking changes
• 🚀 New functionality
• 🐛 Bug fix
• 🧹 Chore
• 📋 Documentation changes/updates
• ♨️ Hot fix
• 🔨 Markdown files fix - not related to source code
• 💅 Polish code

Checklist:

• Tests have been added
• Documentation has been added (Run npm run docs)
• Lint checking (Run npm run lint)
• Local tests are passed (Run npm test)

[kobenguyent]

@danielrentz I'm not sure if the \ here is intended?

[danielrentz]

@kobenguyent As mentioned above... "Unrelated changes in plugins.md have been auto-generated by npm run docs."

No idea what to do about it. Even the git commit hooks manipulate these files, and confusingly in another way than the local build scripts. Will try to remove this change.

Another question... You changed the target branch from 3.x to 4.x a few weeks ago ... I did not notice this and thought I did that by mistake somehow, and therefore changed it back to 3.x. I remember that the PR did show dozens or hundrets of changed files when it has targeted 4.x. What is the desired way here? Is 3.x dead, and work continues in 4.x?

[kobenguyent]

Hi, great news! The 4.x version is now synced with 3.x. As you know, 4.x is an ESM migration, and I believe we’d like to merge into 4.x as much as possible, rather than keeping both 2 branches separate. Perhaps @DavertMik has a different perspective, and I’d love to hear your thoughts. Thanks!