Skip to content

fix: response.data type should not be unknown if endpoint has both 20x and 301/302 response types#220

Merged
gr2m merged 2 commits intomasterfrom
219/response-data-type-fixes
Dec 4, 2020
Merged

fix: response.data type should not be unknown if endpoint has both 20x and 301/302 response types#220
gr2m merged 2 commits intomasterfrom
219/response-data-type-fixes

Conversation

@gr2m
Copy link
Copy Markdown
Contributor

@gr2m gr2m commented Dec 4, 2020 •
edited
Loading

fixes #219

@gr2m gr2m added Type: Bug Something isn't working as documented, or is being fixed typescript Relevant to TypeScript users only labels Dec 4, 2020
@gr2m gr2m merged commit 6cbee66 into master Dec 4, 2020
@gr2m gr2m deleted the 219/response-data-type-fixes branch December 4, 2020 22:05
@octokitbot
Copy link
Copy Markdown
Contributor

octokitbot commented Dec 4, 2020

🎉 This PR is included in version 6.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Type: Bug Something isn't working as documented, or is being fixed typescript Relevant to TypeScript users only

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Endpoints["GET /repos/{owner}/{repo}/issues"]["response"]["data"] is unknown

2 participants

@gr2m @octokitbot