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.

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

added custom 409 response #56

Merged
merged 2 commits into from
Mar 15, 2023
Merged

added custom 409 response #56

merged 2 commits into from
Mar 15, 2023

Conversation

rm-Umar
Copy link
Contributor

@rm-Umar rm-Umar commented Mar 15, 2023

No description provided.

@rm-Umar rm-Umar requested a review from UmanShahzad March 15, 2023 05:36
Copy link
Contributor

@UmanShahzad UmanShahzad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not the right place to put this I'd say, and not like this either, seems like a huge hack to pretend like this is the real response.

We should be checking the actual response code on the client of this library and printing the message. Or modifying the String function of ErrorResponse so that if it's 429 status code, we print our custom msg.

@rm-Umar rm-Umar requested a review from UmanShahzad March 15, 2023 06:57
@UmanShahzad UmanShahzad merged commit c483fc1 into master Mar 15, 2023
@UmanShahzad UmanShahzad deleted the 429-error-response branch March 15, 2023 07:11
@UmanShahzad
Copy link
Contributor

@rm-Umar let's make a new release then for this (patch vsn) and make it available to the cli!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants