@powersync/diagnostics 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/devtools/assets/{powersync-B1PBHXj2.js → powersync-CHeJS2lE.js} +20 -20
- package/dist/devtools/assets/powersync-lB_i3nJt.css +1 -0
- package/dist/devtools/powersync.html +2 -2
- package/dist/rozenite.json +1 -1
- package/lib/src/agent.d.ts +1 -1
- package/lib/src/agent.js.map +1 -1
- package/lib/src/js-agent.js +5 -1
- package/lib/src/js-agent.js.map +1 -1
- package/lib/tsconfig.tsbuildinfo +1 -1
- package/package.json +3 -3
- package/src/agent.ts +2 -0
- package/src/js-agent.ts +5 -1
- package/dist/devtools/assets/powersync-CpTiA65L.css +0 -1
package/README.md
CHANGED
|
@@ -137,6 +137,8 @@ The port can run any SQL and read the sync token, so `attachIframe` only hands i
|
|
|
137
137
|
|
|
138
138
|
**Clear & re-sync** in DevTools deletes the local rows, which is slow on a large database. A host with a throwaway client, like the PowerSync Dashboard, can pass `attachIframe` a wrapper whose `action` handles `clearData` itself and whose other methods call the integration's. Write each method out, because `{ ...integration }` copies none of them and TypeScript does not catch it. Do not delete a real app's database files, because the client would get a new client id. `disconnectAndClear()` keeps the existing one.
|
|
139
139
|
|
|
140
|
+
A host that has the deployed Sync Config, like the PowerSync Dashboard, can add its Sync Streams to what its wrapper's `getInfo` returns, as `streamDefinitions: [{ name, parameters }]`. The Streams tab then suggests them in its subscribe form and shows the parameters each one reads.
|
|
141
|
+
|
|
140
142
|
## MCP
|
|
141
143
|
|
|
142
144
|
Every host exposes the same tools. Names are `powersync_<function>`. Arguments are positional, `arg0` first. React Native has no MCP endpoint: the same tools are Rozenite agent tools (`query`, `schema`, `info`, `status`, `upload-queue`, `action`) with named arguments, for the one database passed to the hook. See [React Native](#react-native).
|