LWhat I haven't heard is that I'm wrong and it's not as easy as I think, but I do wonder if that's true.I said this multiple times
L
L
B
J
idFromName
{ name : undefined }?JLDurableObjectId, which is used both on the caller side of the RPC and inside the DO. In the caller side the .name will be populated correctly. The fact it's not populated inside the DO is a long-term known bug.JLJfirstDO.index() and secondDO.index() to get the list of the items. but I want to include the name of the DO in the list. Ideally it could be done within the index() function and not after.LJJL
J.name property
NN
LJsetIdentifier every time they "get" an Actor instance (which is a Durable Object) and refer to this.identifier rather than try to parse the name out of the id. It's very little code and works the same in dev and production.LLI'm basically using all RPC calls I thinkI hear people say this and I always wonder how users enter the system? It's got to be HTTP or WebSockets, no?
LLJfirstDO.withIdentifier('user:123').index()Jfetch()fetch () and routing it that wayJBindDurableObjectMiddleware is what sets the DO to c.var.notifications
1
CCLLJN
GG
PJL
CC
M
ctx: DurableObjectState { ...,
id: DurableObjectId { name: undefined }
}{ name : undefined }DurableObjectId.name.namefirstDO.index()secondDO.index()index()setIdentifierthis.identifierfirstDO.withIdentifier('user:123').index()fetch ()BindDurableObjectMiddlewarec.var.notifications {
"tag": "v3",
"deleted_classes": [
"UserCreditsObject"
],
"new_sqlite_classes": [
"UserCreditsObject"
]
}app.get("/:id", HonoAuthMiddleware, BindDurableObjectMiddleware, async (c) => {
const id = c.req.param("id");
const notification = await c.var.notifications.get(id);
if (!notification) return c.body(null, 204);
return c.json(notification);
});