fix: page.goto options type should be optional (#6038)

The TypeScript definition erroneously made `options` required. We can
fix it by providing a default value, which means users calling the
function will be able to leave it blank without TS complaining.

Issues like this are a +1 to porting our tests to TypeScript in order to
catch these on our own test suite, so that's something we should look into.
This commit is contained in:
Jack Franklin 2020-06-18 12:44:46 +01:00 committed by GitHub
parent 44402b75a0
commit ce34c0a4ff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 4 additions and 4 deletions

View File

@ -7,7 +7,7 @@
<b>Signature:</b>
```typescript
goto(url: string, options: {
goto(url: string, options?: {
referer?: string;
timeout?: number;
waitUntil?: PuppeteerLifeCycleEvent | PuppeteerLifeCycleEvent[];

View File

@ -7,7 +7,7 @@
<b>Signature:</b>
```typescript
goto(url: string, options: WaitForOptions & {
goto(url: string, options?: WaitForOptions & {
referer?: string;
}): Promise<HTTPResponse>;
```

View File

@ -412,7 +412,7 @@ export class Frame {
referer?: string;
timeout?: number;
waitUntil?: PuppeteerLifeCycleEvent | PuppeteerLifeCycleEvent[];
}
} = {}
): Promise<HTTPResponse | null> {
return await this._frameManager.navigateFrame(this, url, options);
}

View File

@ -838,7 +838,7 @@ export class Page extends EventEmitter {
async goto(
url: string,
options: WaitForOptions & { referer?: string }
options: WaitForOptions & { referer?: string } = {}
): Promise<HTTPResponse> {
return await this._frameManager.mainFrame().goto(url, options);
}