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

chore: fix response attribute from AppwriteException #1031

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

ChiragAgg5k
Copy link
Member

@ChiragAgg5k ChiragAgg5k commented Jan 24, 2025

What does this PR do?

The response attribute in AppwriteException seems to sometimes be an object even though it should be a string. This PR fixes typing for response attribute and adds relevant tests for it.

image

Test Plan

  1. android
  2. apple
  3. cli
  4. dart
  5. deno
  6. dotnet
  7. flutter
  8. go
  9. `graphql
  10. kotlin
  11. node
  12. php
  13. python
  14. react-native
  15. rest
  16. ruby
  17. swift
  18. web

Related PRs and Issues

Have you read the Contributing Guidelines on issues?

Yes.

@ChiragAgg5k ChiragAgg5k requested a review from loks0n January 24, 2025 09:11
@ChiragAgg5k ChiragAgg5k force-pushed the fix-execption-response branch from b0991da to 1447dba Compare January 27, 2025 16:06
@ChiragAgg5k ChiragAgg5k changed the title fix: added type response for appwriteexecption fix: fixed response type for AppwriteExecption Jan 27, 2025
loks0n

This comment was marked as resolved.

@loks0n
Copy link
Member

loks0n commented Jan 27, 2025

Also Swift and Dotnet tests are failing, can you look into it?

@ChiragAgg5k ChiragAgg5k force-pushed the fix-execption-response branch from fbc1eb1 to 6e45683 Compare January 28, 2025 10:50
@ChiragAgg5k ChiragAgg5k changed the title fix: fixed response type for AppwriteExecption chore: remove response attribute from AppwriteExecption Jan 28, 2025
@ChiragAgg5k ChiragAgg5k changed the title chore: remove response attribute from AppwriteExecption chore: remove response attribute from AppwriteException Jan 28, 2025
@ChiragAgg5k ChiragAgg5k force-pushed the fix-execption-response branch from 6e45683 to 1ec4519 Compare January 29, 2025 10:47
@ChiragAgg5k ChiragAgg5k changed the title chore: remove response attribute from AppwriteException chore: fix response attribute from AppwriteException Jan 29, 2025
@@ -490,7 +490,7 @@ class Client @JvmOverloads constructor(
body
)
} else {
{{ spec.title | caseUcfirst }}Exception(body, response.code)
{{ spec.title | caseUcfirst }}Exception(body, response.code, "", body)
Copy link
Member

Choose a reason for hiding this comment

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

Should we set the type (third) parameter?

Copy link
Member Author

Choose a reason for hiding this comment

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

Screenshot 2025-02-06 at 8 24 21 PM

when the response is in plain text, we don't have a type returned by the backend. we can manually set it as type: text, but that conveys the message was expected to be of type text, which it wasn't

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.

3 participants