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

How detect HTTP RESPONSES different than 200 on paginated objects? #4

Open
pitbulk opened this issue Oct 3, 2017 · 0 comments
Open

How detect HTTP RESPONSES different than 200 on paginated objects? #4

pitbulk opened this issue Oct 3, 2017 · 0 comments

Comments

@pitbulk
Copy link
Contributor

pitbulk commented Oct 3, 2017 •
edited
Loading

@richet

Previously the SDK was able to detect if a paginated query returned a non 200 response, but after the cursor refactor, we are not able to detect when API returns 400 or 401.
@pitbulk pitbulk changed the title How retrieve errors on paginated objects? How detect HTTP RESPONSES different than 200 on paginated objects? Oct 3, 2017
pitbulk added a commit that referenced this issue Jul 7, 2018
@pitbulk
Fix #4. Add to Cursor error and error_description attributes based on…
a0231ea 
… response
@pitbulk pitbulk mentioned this issue Jul 7, 2018
Open
pitbulk added a commit that referenced this issue Nov 27, 2018
@pitbulk
Fix issue with error code at regenerate_token method. Move extract_er…
5ab4b9d 
…ror_message_from_response and extract_error_attribute_from_response to an specific class. See #4 Create ApiException that will be raised on Cursor when OneLogin API returns an error
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
@pitbulk