Skip to content

feat: React Native SDK update for version 0.32.0#108

Merged
ChiragAgg5k merged 6 commits into
mainfrom
dev
Jun 8, 2026
Merged

feat: React Native SDK update for version 0.32.0#108
ChiragAgg5k merged 6 commits into
mainfrom
dev

Conversation

@ChiragAgg5k

@ChiragAgg5k ChiragAgg5k commented Jun 8, 2026

Copy link
Copy Markdown
Member

This PR contains updates to the React Native SDK for version 0.32.0.

@ChiragAgg5k ChiragAgg5k changed the title feat: React Native SDK update for version 0.32.0 feat: SDK update for version 0.32.0 Jun 8, 2026
@greptile-apps

greptile-apps Bot commented Jun 8, 2026

Copy link
Copy Markdown

Greptile Summary

This PR updates the React Native SDK to version 0.32.0 with several breaking changes and additions. The Theme enum is renamed to BrowserTheme, Models.DefaultPresence is removed along with the Presence generic from presences methods, and all requests now send an explicit accept header matching each endpoint's response type.

  • Two new services are introduced: Presences (list/get/upsert/update/delete presence logs) and TablesDB (transaction management and row-level CRUD with optional transaction IDs), each following the existing dual-overload parameter style.
  • models.ts is updated to add Presence.metadata, Membership.userAccessedAt, and email metadata fields to User, consistent with the changelog.
  • Both presences.ts and tables-db.ts carry dead imports (FileSystem from expo-file-system and Platform as RNPlatform) that are never used — the same pattern previously flagged in apps.ts and oauth-2.ts.

Confidence Score: 5/5

Safe to merge; the breaking changes are well-documented and the new service implementations follow established patterns correctly.

The core logic changes are straightforward: an enum rename, model field additions, and two new services that mirror the existing dual-overload SDK pattern. The previously flagged missing return statement in createExecution is present and correct in this version. The only findings are dead imports in the two new service files, which do not affect runtime behaviour.

No files require special attention beyond the cosmetic unused-import cleanup in src/services/presences.ts and src/services/tables-db.ts.

Important Files Changed

Filename Overview
src/services/functions.ts createExecution now correctly issues the HTTP call (the previously missing return statement is present); unused FileSystem/RNPlatform imports remain but are pre-existing.
src/services/presences.ts New Presences service with list/get/upsert/update/delete operations; contains unused FileSystem and RNPlatform imports that should be removed.
src/services/tables-db.ts New TablesDB service with transaction/row CRUD; same unused FileSystem and RNPlatform imports as presences.ts.
src/enums/browser-theme.ts New BrowserTheme enum (Light/Dark) replacing the old Theme enum; correctly exported from index.ts.
src/models.ts Adds Presence.metadata, Membership.userAccessedAt, and email metadata fields to User; removes DefaultPresence as advertised in the changelog.
src/index.ts Exports BrowserTheme replacing Theme, and adds Presences/TablesDB exports; all symbols appear consistent with implementation.

Reviews (6): Last reviewed commit: "chore: update React Native SDK to 0.32.0" | Re-trigger Greptile

Comment thread src/services/apps.ts Outdated
@ChiragAgg5k ChiragAgg5k changed the title feat: SDK update for version 0.32.0 feat: React Native SDK update for version 0.32.0 Jun 8, 2026
# Conflicts:
#	package-lock.json
#	package.json
#	src/client.ts
@ChiragAgg5k ChiragAgg5k changed the title feat: React Native SDK update for version 0.32.0 feat: SDK update for version 0.32.0 Jun 8, 2026
@ChiragAgg5k ChiragAgg5k changed the title feat: SDK update for version 0.32.0 feat: React Native SDK update for version 0.32.0 Jun 8, 2026
Comment thread src/services/functions.ts
@ChiragAgg5k ChiragAgg5k merged commit 0ce6c63 into main Jun 8, 2026
1 check passed
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