-
Notifications
You must be signed in to change notification settings - Fork 14.5k
[Durable Objects] Address review feedback on ctx.id.name changelog #30897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+42
−39
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
42 changes: 42 additions & 0 deletions
42
src/content/changelog/durable-objects/2026-03-15-durable-object-id-name.mdx
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| --- | ||
| title: Access Durable Object name via `ctx.id.name` | ||
| description: Retrieve the name of a named Durable Object from within the object itself. | ||
| products: | ||
| - durable-objects | ||
| - workers | ||
| date: 2026-03-15 | ||
| --- | ||
|
|
||
| When your Worker accesses a Durable Object via `idFromName()` or `getByName()`, the same name is now available on `ctx.id.name` inside the object — no need to pass it through method arguments or persist it in storage. This brings the runtime behavior in line with the [Workers runtime types](/workers/languages/typescript/). | ||
|
|
||
| This is especially useful for [alarms](/durable-objects/api/alarms/), where there is no calling client to pass the name as an argument. When an alarm handler runs, `ctx.id.name` will hold the same name the object was originally accessed with. | ||
|
|
||
| ```js | ||
| import { DurableObject } from "cloudflare:workers"; | ||
|
|
||
| export class ChatRoom extends DurableObject { | ||
| async getRoomName() { | ||
| // ctx.id.name returns the name passed to getByName() or idFromName() | ||
| return this.ctx.id.name; | ||
| } | ||
| } | ||
|
|
||
| // Worker | ||
| export default { | ||
| async fetch(request, env) { | ||
| const stub = env.CHAT_ROOM.getByName("general"); | ||
| const roomName = await stub.getRoomName(); | ||
| return new Response(`Welcome to ${roomName}!`); | ||
| }, | ||
| }; | ||
| ``` | ||
|
|
||
| `ctx.id.name` is `undefined` in the following cases: | ||
|
|
||
| - For Durable Objects created with `newUniqueId()`. | ||
| - When accessed via `idFromString()`, even if the ID was originally created from a name. | ||
| - For [names longer than 1,024 bytes](/durable-objects/api/id/#name). | ||
|
|
||
| This works the same way in local development with `wrangler dev` as it does in production. Run `npm update wrangler` to ensure you are on a version with this support. | ||
|
|
||
| For more information, refer to the [Durable Object ID documentation](/durable-objects/api/id/#name). | ||
39 changes: 0 additions & 39 deletions
39
src/content/changelog/durable-objects/2026-03-26-durable-object-id-name.mdx
This file was deleted.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.