Skip to content
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

Jump to bottom

why apiResponseCode and not httpResponseCode #865

Open
loic425 opened this issue Apr 9, 2024 · 0 comments
Open

why apiResponseCode and not httpResponseCode #865

loic425 opened this issue Apr 9, 2024 · 0 comments

Comments

@loic425
Copy link
Member

loic425 commented Apr 9, 2024

Not within scope of current PR and just thinking out load -- I find these exceptions strange, why apiResponseCode and not httpResponseCode or why it need this property at all, it doesn't feel like resource exception, but rather like some app-level exception.

Originally posted by @diimpp in #768 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@loic425