feat!: useShapeQuery prend le Scope du SDK, et un store se nomme par sa reference
This commit is contained in:
@@ -525,7 +525,7 @@ test("nothing about the deferred service reaches the published surface", () => {
|
||||
"subscribeDoc",
|
||||
"subscribeDocs",
|
||||
"useShape",
|
||||
"watchShape",
|
||||
"useShapeQuery",
|
||||
]);
|
||||
expect(Object.keys(polyfill.inbox).sort()).toEqual([
|
||||
"post",
|
||||
@@ -547,11 +547,14 @@ test("nothing about the deferred service reaches the published surface", () => {
|
||||
"sparqlQuery",
|
||||
"sparqlUpdate",
|
||||
]);
|
||||
// `1.0.0-dev.5`: `listMyEntityDocs`, `resolveScopeGraph` and `resolveWriteGraph` left,
|
||||
// and the three store accessors arrived in their place — an application names a store by
|
||||
// the reference one of them hands it, never by a word this package made up.
|
||||
expect(Object.keys(polyfill.storeRegistry).sort()).toEqual([
|
||||
"createEntityDoc",
|
||||
"listMyEntityDocs",
|
||||
"openDocumentInbox",
|
||||
"resolveScopeGraph",
|
||||
"resolveWriteGraph",
|
||||
"privateStore",
|
||||
"protectedStore",
|
||||
"publicStore",
|
||||
]);
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user