You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(json-render): support native RPC contexts in browser surfaces
Tracked in dvcol/devkit-extension#12. Preserve existing renderer context defaults, expose the prebuilt browser renderer and portable view publication, and clean up failed mounts. Scoped lint, type checks, existing renderer tests and live extension proof pass.
`call` and `sharedState` are native RPC members. An optional `connectionMeta.backend` marks static output. The reference implementation accepts this smaller `JsonRenderRpcContext`; a full hub client context also satisfies it. Custom `JsonRenderDockRenderer` implementations retain the full client context by default and can declare their own context type through its generic parameter.
189
+
190
+
For view publication in a worker, import `createJsonRenderView` from `@devframes/json-render/view` and pass `{ rpc: { sharedState } }`. Its native publishing state must support `get(key, { sharedState })`. The node-side import and scoped node contexts continue to use the same implementation.
0 commit comments