feat: Web SDK update for version 26.0.0#175
Conversation
# Conflicts: # package-lock.json # package.json # src/client.ts
Greptile SummaryThis PR bumps the Web SDK to version 26.0.0, introducing several breaking changes and new fields across models and services. All service methods are updated to pass
Confidence Score: 4/5Safe to merge with one model type fix recommended before release. The bulk of the change is a mechanical, generated update that correctly threads X-Appwrite-Project through every service call. The one substantive concern is Membership.userAccessedAt being typed as a required string when its JSDoc explicitly says "Show this attribute by toggling membership privacy in the Console" — meaning the field is absent from API responses by default. src/models.ts — the Membership.userAccessedAt field type Important Files Changed
Reviews (5): Last reviewed commit: "chore: update Web SDK to 26.0.0" | Re-trigger Greptile |
| const apiHeaders: { [header: string]: string } = { | ||
| 'X-Appwrite-Project': this.client.config.project, | ||
| 'accept': 'image/png', | ||
| } |
There was a problem hiding this comment.
Unused
apiHeaders block in URL-building methods
All eight avatar methods return uri.toString() directly without calling this.client.call(). The apiHeaders object (including the newly added X-Appwrite-Project and accept values) is declared but never passed anywhere and has no effect. The same pattern is also present in the three URL-building methods in storage.ts (download, preview, view). The project identity is correctly carried via payload['project'] appended as a query parameter; the dead apiHeaders block just adds noise and could mislead maintainers.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| Dark = 'dark', | ||
| } No newline at end of file |
| return this.client.chunkedUpload( | ||
| 'post', | ||
| uri, | ||
| apiHeaders, | ||
| payload | ||
| payload, | ||
| onProgress | ||
| ); |
There was a problem hiding this comment.
createExecution always throws "File not found in payload"
chunkedUpload (line 910 in client.ts) immediately throws Error: 'File not found in payload' when no File instance is found in the payload. The createExecution payload only ever contains strings, booleans, and plain objects — never a File — so every call to createExecution will throw this error unconditionally, making the function completely non-functional in this release.
This PR contains updates to the Web SDK for version 26.0.0.