Repository navigation
feat: Python SDK update for version 25.0.0 - #164
Conversation
ChiragAgg5k
changed the title
🔵 Tier A · Mergeable after minor fixes
This update brings the Python SDK to 25.0.0, targets Appwrite response format 2.5.0, and adds new query, topic, restoration, proxy, and function capabilities. It also updates response models and removes APIs and models that were retired for this server version. 385 of 475 changed files were too large to include in full.
Note Not approving while a bug finding is open: Default missing preference maps to an empty map
Fix with agent prompt### Issue 1
appwrite/models/account.py:129
**Default missing preference maps to an empty map**
When a response omits `prefs`, this validator still leaves the required field unset, so `Account.model_validate()` raises instead of applying the `{}` default described for missing map fields. `User` and `Organization` have the same gap, so those responses still cannot benefit from the new missing-field fallback.
### Issue 2
test/services/test_proxy.py:204-206
**SMTP rule test does not verify an SMTP request**
This mock accepts every method and URL, and the fixture above reports `protocol: http`, so the test still passes if `create_smtp_rule` calls the wrong route or returns a non-SMTP rule. Register the expected POST endpoint and assert the SMTP protocol (and request fields) so this test covers the new contract.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.📂 Walkthrough · 6
⏳ Still open from earlier reviews · 1
Reviewed |
![hansi-codes[bot]](https://avatars.githubusercontent.com/in/5046327?s=60&v=4){kind=small}
ChiragAgg5k
changed the title
| m.request( | ||
| requests_mock.ANY, | ||
| requests_mock.ANY, |
There was a problem hiding this comment.
SMTP rule test does not verify an SMTP request
This mock accepts every method and URL, and the fixture above reports protocol: http, so the test still passes if create_smtp_rule calls the wrong route or returns a non-SMTP rule. Register the expected POST endpoint and assert the SMTP protocol (and request fields) so this test covers the new contract.
Prompt To Fix With AI
This is a comment left during a code review.
Path: test/services/test_proxy.py
Line: 204-206
Comment:
**SMTP rule test does not verify an SMTP request**
This mock accepts every method and URL, and the fixture above reports `protocol: http`, so the test still passes if `create_smtp_rule` calls the wrong route or returns a non-SMTP rule. Register the expected POST endpoint and assert the SMTP protocol (and request fields) so this test covers the new contract.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟡 Minor · testing · Reply if this doesn't apply.
|
@hansi-codes review |
|
@hansi-codes review |
| data['targets'] = [] | ||
| if 'accessedAt' not in data and 'accessedat' not in data: | ||
| data['accessedAt'] = '' | ||
| return data |
There was a problem hiding this comment.
Default missing preference maps to an empty map
When a response omits prefs, this validator still leaves the required field unset, so Account.model_validate() raises instead of applying the {} default described for missing map fields. User and Organization have the same gap, so those responses still cannot benefit from the new missing-field fallback.
Prompt To Fix With AI
This is a comment left during a code review.
Path: appwrite/models/account.py
Line: 129
Comment:
**Default missing preference maps to an empty map**
When a response omits `prefs`, this validator still leaves the required field unset, so `Account.model_validate()` raises instead of applying the `{}` default described for missing map fields. `User` and `Organization` have the same gap, so those responses still cannot benefit from the new missing-field fallback.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟡 Minor · bug · Reply if this doesn't apply.
1 participant
This PR contains updates to the SDK for version 25.0.0.
What's Changed
X-Appwrite-Response-Format: 2.5.0; responses follow the 2.5 shapesaccount.list_logs,users.list_logsand theLog/LogListmodelsorganization.create_key,get_key,list_keys,update_keyanddelete_key, andOrganizationKeyScopes; useorganization.list_project_keys,get_project_key,update_project_keyanddelete_project_keyinsteadClient.set_dev_key, theDevKeymodel andProject.dev_keysBillingPlanGroup.STARTER; useBillingPlanGroup.FREElist_specificationsreturns each specification's prices and overage rates on the row itself. Removed the list-levelpricingfield and theDedicatedDatabaseSpecificationPricingmodelBlockfieldsreason,project_name,region,organization_name,organization_idandbilling_planresourceparams now takeList[str]project.update_o_auth2_kakaotakesenabledbeforepromptBackupRestoration.optionsis now a dictOptional, such asBillingPlan.usageandDedicatedDatabase.engineTopichelper to build MQTT topics for push messagesmongo,mysqlandpostgresqlpromote_restoration,restore_mode,target_nameandauto_promoteoncreate_restoration, andDedicatedDatabaseRestoration.restore_modeproxy.create_smtp_rule, theProxyRuleProtocolenum andProxyRule.protocolemail_enabledonfunctions.updateandFunction, andExecutionTrigger.EMAILQueryaggregates (count,count_distinct,sum,avg,min,maxand more),group_by,having,distinct, joins,relationship,covers,spatial_equalsandpageQuery.builder()to chain queries;build()returns the query list{}instead of[]