Support in-memory Syncables imports in browser WASM - #29
Merged
Conversation
This was referenced Sep 9, 2026
michielbdejong
force-pushed
the
codex/browser-integrations
branch
from
September 9, 2026 12:51
0ab3521 to
f30be84
Compare
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
1 participant
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.
Allow browser hosts to run a Syncables import from an already loaded OpenAPI document without opening a filesystem path.
SyncClient::sync_documentand a regression proving the configured path is never opened.Rebased onto current main, including its nullable schema types and nested ontology support. Validation after conflict resolution: all 150 native tests pass; native all-targets Clippy, WASM Clippy and the WASM library build pass.
Companion PRs: ontola/atomic-server#1401 and localthought/integration-proxy#31. Atomic currently vendors the previously verified snapshot; adopting the newer nested-ontology behavior is separate from this conflict resolution.