Skip to content

Clean up grammar #2862

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 9, 2020
Merged

Clean up grammar #2862

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions source/api/commands/route.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Pass in an options object to change the default behavior of `cy.route()`. By def
Option | Default | Description
--- | --- | ---
`delay` | `0` | Delay for stubbed responses (in ms)
`force404` | `false` | Forcibly send XHR's a 404 status when the XHR's do not match any existing {% url `cy.route()` route %}.
`force404` | `false` | Forcibly send a 404 status when the XHR does not match any existing {% url `cy.route()` route %}.
`headers` | `null` | Response headers for stubbed routes
`method` | `GET` | Method to match against requests
`onAbort` | `null` | Callback function which fires anytime an XHR is aborted
Expand Down Expand Up @@ -406,13 +406,13 @@ cy.route(() => {

## Debugging

### Understanding stubbed vs regular XHR's
### Understanding stubbed vs regular XHRs

Cypress indicates whether an XHR sent back a stubbed response or actually went out to a server in its Command Log

XHR's that display `(XHR STUB)` in the Command Log have been stubbed and their response, status, headers, and delay have been controlled by your matching `cy.route()`.
XHRs that display `(XHR STUB)` in the Command Log have been stubbed and their response, status, headers, and delay have been controlled by your matching `cy.route()`.

XHR's that display `(XHR)` in the Command Log have *not* been stubbed and were passed directly through to a server.
XHRs that display `(XHR)` in the Command Log have *not* been stubbed and were passed directly through to a server.

{% imgTag /img/api/route/xhr-stub-versus-not-stubbed-routes-in-command-log.png "XHR Command Log when not stubbed" %}

Expand All @@ -438,7 +438,7 @@ When Cypress matches up an outgoing XHR request to a `cy.route()`, it actually a
cy.route('**/users/*')
```

The following XHR's which were `xhr.open(...)` with these URLs would:
The following XHRs which were `xhr.open(...)` with these URLs would:

**Match:**

Expand Down Expand Up @@ -490,7 +490,7 @@ Whenever you start a server and add routes, Cypress will display a new Instrumen

{% imgTag /img/api/route/routing-table-displayed-in-command-log-for-cy-route.png "Command Log routing table" %}

When XHR's are made, Cypress will log them in the Command Log and indicate whether they matched a routing alias:
When XHRs are made, Cypress will log them in the Command Log and indicate whether they matched a routing alias:

{% imgTag /img/api/route/some-xhr-responses-including-200-and-500-status-codes.png "Command Log XHR alias route" %}

Expand Down