Repository navigation
[party-stack] Upgrade persistence and Expo runtime support - #188
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 8215cc6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 20 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or 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
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.
This updates persistence and mobile runtime support needed by the Streamline migration, and adds awaitable Foundry collection refresh without recreating installations.
Changes
collection.utils.refresh(). Foundry replaces rows atomically from a fresh source snapshot, keeps subscriptions alive, replays queued live updates, and propagates errors. Reconnect and operation acknowledgement use fresh snapshots when edit history is unavailable.@party-stack/expo-runtime/polyfillentry point for Expo Blob and a compatible global File; retain Expo's default fetch. Cover Expo FormData filename handling.Validation
pnpm exec vp run ci— all 126 tasks pass, including checks, builds, and tests.Expo native APIs are mocked in runtime tests; a simulator/device attachment round trip remains to be verified. Consumers must upgrade to Expo SDK 57 and import the polyfill before application code. No legacy Expo filesystem migration is included because this runtime has no production installations.