Tags: datashaman/request.js
Toggle v5.3.1's commit message
chore(package): update lockfile package-lock.json
Toggle v5.3.0's commit message
test: make TypeScript happy 🤷🏾♀️
Toggle v5.2.1's commit message
fix(package): version in published package
Toggle v5.2.0's commit message
feat: add server validation errors to error message (octokit#91 )
Toggle v5.1.0's commit message
test: README authentication example
Toggle v5.0.3's commit message
refactor: adapt for universal-user-agent@v4
Toggle v5.0.2's commit message
fix: pass request-compatible API to `request.hook(request, options)`
Toggle v5.0.1's commit message
chore(package): update lockfile package-lock.json
Toggle v5.0.0's commit message
feat: `options.request.hook`’s signature is now `(request, endpointOp…
…tions)`
BREAKING CHANGE: `options.request.hook`’s signature is now `(request, endpointOptions)`
Before:
```js
request("GET /user", { request: { hook: (options, request) => /* ... */ } })
```
After:
```js
request("GET /user", { request: { hook: (request, options) => /* ... */ } })
```
That way it aligns with `octokit.hook` from `@octokit/rest`
Toggle v4.1.1's commit message
build(package): publish to `@next` dist-tag to be sure, as publish se…
…tup changed
You can’t perform that action at this time.