Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: ensure docs include @returns Promise<void> where appropriate #3954

Merged
merged 1 commit into from
Oct 28, 2023

Conversation

fwouts
Copy link
Contributor

@fwouts fwouts commented Oct 27, 2023

Motivation/Description of the PR

This PR fixes the generated typings/types.d.ts definitions for methods that use Mustache docs. The intention is similar to #3465, but it fixes the original helper types instead.

Note that there are still various methods that aren't typed properly, such as Playwright._getPageUrl() (currently typed as void), because they are missing @return JSDoc annotations. This should also be fixed, although it may make more sense to do this in a separate PR to keep this one focused.

This fixes #3324.

Applicable helpers:

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

Type of change

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

Checklist:

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

@kobenguyent kobenguyent added documentation typescript Changes for typings or typescript compatibility labels Oct 27, 2023
@kobenguyent
Copy link
Collaborator

Thank you @fwouts

@kobenguyent kobenguyent merged commit 8b721ca into codeceptjs:3.x Oct 28, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation typescript Changes for typings or typescript compatibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Discrepancies between code documentation online and the NPM package
2 participants