Commit adf83c6

authored

Update article.md

1 parent 80eb70f commit adf83c6Copy full SHA for adf83c6

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -363,7 +363,7 @@ More explanations about how it works:`
`363`	`363`	- The initial URL is `https://api.github.com/repos/<repo>/commits`, and the next page will be in the `Link` header of the response.
`364`	`364`	- The `fetch` method allows us to supply authorization and other headers if needed -- here GitHub requires `User-Agent`.
`365`	`365`	`2. The commits are returned in JSON format.`
`366`		-3. We should get the next page URL from the `Link` header of the response. It has a special format, so we use a regular expression for that (we will lern this feature in [Regular expressions](info:regular-expressions)).
	`366`	+3. We should get the next page URL from the `Link` header of the response. It has a special format, so we use a regular expression for that (we will learn this feature in [Regular expressions](info:regular-expressions)).
`367`	`367`	- The next page URL may look like `https://api.github.com/repositories/93253246/commits?page=2`. It's generated by GitHub itself.
`368`	`368`	4. Then we yield the received commits one by one, and when they finish, the next `while(url)` iteration will trigger, making one more request.
`369`	`369`

Comments

(0)