Filip/playwright
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs: fix route.fallback typo (#15173)

Browse source
This commit is contained in:
Sébastien Règne 2022-06-28 22:46:54 +02:00 committed by GitHub
parent 2a01d0c83c
commit f43fe4855d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/src/api/class-route.md
View file

@ -117,7 +117,7 @@ If set changes the request HTTP headers. Header values will be converted to a st
## async method: Route.fallback ## async method: Route.fallback
When several routes match the given pattern, they run in the order opposite to their registration. When several routes match the given pattern, they run in the order opposite to their registration.
That way the last registered route can always override all the previos ones. In the example below, That way the last registered route can always override all the previous ones. In the example below,
request will be handled by the bottom-most handler first, then it'll fall back to the previous one and request will be handled by the bottom-most handler first, then it'll fall back to the previous one and
in the end will be aborted by the first registered route. in the end will be aborted by the first registered route.

2
packages/playwright-core/types/types.d.ts vendored
View file

@ -15287,7 +15287,7 @@ export interface Route {
/** /**
* When several routes match the given pattern, they run in the order opposite to their registration. That way the last * When several routes match the given pattern, they run in the order opposite to their registration. That way the last
* registered route can always override all the previos ones. In the example below, request will be handled by the * registered route can always override all the previous ones. In the example below, request will be handled by the
* bottom-most handler first, then it'll fall back to the previous one and in the end will be aborted by the first * bottom-most handler first, then it'll fall back to the previous one and in the end will be aborted by the first
* registered route. * registered route.
* *