-
Notifications
You must be signed in to change notification settings - Fork 175
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
ChiragAgg5k
wants to merge
7
commits into
master
Choose a base branch
from
fix-execption-response
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+133
−43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
loks0n
reviewed
Jan 24, 2025
templates/android/library/src/main/java/io/package/exceptions/Exception.kt.twig
Outdated
Show resolved
Hide resolved
templates/kotlin/src/main/kotlin/io/appwrite/exceptions/Exception.kt.twig
Outdated
Show resolved
Hide resolved
ChiragAgg5k
force-pushed
the
fix-execption-response
branch
from
January 27, 2025 16:06
b0991da
to
1447dba
Compare
ChiragAgg5k
changed the title
fix: added type response for appwriteexecption
fix: fixed response type for AppwriteExecption
Jan 27, 2025
loks0n
reviewed
Jan 27, 2025
Also Swift and Dotnet tests are failing, can you look into it? |
ChiragAgg5k
force-pushed
the
fix-execption-response
branch
from
January 28, 2025 10:50
fbc1eb1
to
6e45683
Compare
ChiragAgg5k
changed the title
fix: fixed response type for AppwriteExecption
chore: remove response attribute from AppwriteExecption
Jan 28, 2025
ChiragAgg5k
changed the title
chore: remove response attribute from AppwriteExecption
chore: remove response attribute from AppwriteException
Jan 28, 2025
ChiragAgg5k
force-pushed
the
fix-execption-response
branch
from
January 29, 2025 10:47
6e45683
to
1ec4519
Compare
ChiragAgg5k
changed the title
chore: remove response attribute from AppwriteException
chore: fix response attribute from AppwriteException
Jan 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The
response
attribute in AppwriteException seems to sometimes be anobject
even though it should be a string. This PR fixes typing for response attribute and adds relevant tests for it.Test Plan
android
apple
cli
dart
deno
dotnet
flutter
go
kotlin
node
php
python
react-native
rest
ruby
swift
web
Related PRs and Issues
response
prop ofAppwriteException
declaresstring
, but the response is actually anobject
#1017Have you read the Contributing Guidelines on issues?
Yes.