-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[Docs Site] core formatting checks #17262
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
Merged
Changes from 2 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
ab344f5
chore: core formatting checks
Cherry abcd051
chore: format left-over files
Cherry 884dba0
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry 013b1bd
Merge branch 'production' into chore/formatting
Cherry fea05dc
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry a1c7d78
chore: more formatting
Cherry 6ce7a4b
chore: more formatting
Cherry d83f81c
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry 195e631
chore: format more
Cherry 0ab5b84
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry 49c9d88
chore: format more
Cherry b11dc01
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry ec5bb23
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry 6e1fac9
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry 8793f7b
chore: format
Cherry 6e1817d
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry b4af0a5
chore: update formatting
Cherry 826194b
Merge remote-tracking branch 'upstream/production' into chore/formatting
Cherry f11a718
Update package.json
Cherry 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
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
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
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
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
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
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
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
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
Large diffs are not rendered by default.
Oops, something went wrong.
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 |
|---|---|---|
| @@ -1,65 +1,65 @@ | ||
| --- | ||
| productName: Durable Objects | ||
| entries: | ||
| - term: "Durable Objects" | ||
| general_definition: |- | ||
| The product name, or the collective noun referring to more than one Durable Object instance. | ||
| - term: "Durable Objects" | ||
| general_definition: |- | ||
| The product name, or the collective noun referring to more than one Durable Object instance. | ||
|
|
||
| - term: "Namespace" | ||
| general_definition: |- | ||
| A container for a collection of Durable Objects that all share the same Durable Object (class) definition. A single Namespace can have (tens of) millions of Durable Objects. Metrics are scoped per Namespace. | ||
| - term: "Namespace" | ||
| general_definition: |- | ||
| A container for a collection of Durable Objects that all share the same Durable Object (class) definition. A single Namespace can have (tens of) millions of Durable Objects. Metrics are scoped per Namespace. | ||
|
|
||
| - term: "Durable Object" | ||
| general_definition: |- | ||
| An individual Durable Object. A Durable Object is globally unique (referenced by ID), provides a global point of coordination for all methods/requests sent to it, and has private, persistent storage that is not shared with other Durable Objects within a Namespace. | ||
| - term: "Durable Object" | ||
| general_definition: |- | ||
| An individual Durable Object. A Durable Object is globally unique (referenced by ID), provides a global point of coordination for all methods/requests sent to it, and has private, persistent storage that is not shared with other Durable Objects within a Namespace. | ||
|
|
||
| - term: "Stub" | ||
| general_definition: |- | ||
| An object that refers to a unique Durable Object within a Namespace and allows you to call into that Durable Object via RPC methods or the `fetch` API. For example, `let stub = env.MY_DURABLE_OBJECT.get(id)` | ||
| - term: "Stub" | ||
| general_definition: |- | ||
| An object that refers to a unique Durable Object within a Namespace and allows you to call into that Durable Object via RPC methods or the `fetch` API. For example, `let stub = env.MY_DURABLE_OBJECT.get(id)` | ||
|
|
||
| - term: "actor" | ||
| general_definition: |- | ||
| A term referring to a unique Durable Object. | ||
| - term: "actor" | ||
| general_definition: |- | ||
| A term referring to a unique Durable Object. | ||
|
|
||
| - term: "instance" | ||
| general_definition: |- | ||
| See 'actor'. | ||
| - term: "instance" | ||
| general_definition: |- | ||
| See 'actor'. | ||
|
|
||
| - term: "Durable Object class" | ||
| general_definition: |- | ||
| The JavaScript class that defines the methods (RPC) and handlers (`fetch`, `alarm`) as part of your Durable Object, and/or an optional `constructor`. All Durable Objects within a single Namespace share the same class definition. | ||
| - term: "Durable Object class" | ||
| general_definition: |- | ||
| The JavaScript class that defines the methods (RPC) and handlers (`fetch`, `alarm`) as part of your Durable Object, and/or an optional `constructor`. All Durable Objects within a single Namespace share the same class definition. | ||
|
|
||
| - term: "Storage Backend" | ||
| general_definition: |- | ||
| By default, a Durable Object class can use Storage API that leverages a key-value storage backend. New Durable Object classes can opt-in to using a [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). | ||
| - term: "Storage Backend" | ||
| general_definition: |- | ||
| By default, a Durable Object class can use Storage API that leverages a key-value storage backend. New Durable Object classes can opt-in to using a [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). | ||
|
|
||
| - term: "Storage API" | ||
| general_definition: |- | ||
| The transactional and strongly consistent (serializable) [Storage API](/durable-objects/api/storage-api/) for persisting data within each Durable Object instance. State stored within a unique DO instance is "private" to that Durable Object, and not accessible from other Durable Objects. | ||
| - term: "Storage API" | ||
| general_definition: |- | ||
| The transactional and strongly consistent (serializable) [Storage API](/durable-objects/api/storage-api/) for persisting data within each Durable Object instance. State stored within a unique DO instance is "private" to that Durable Object, and not accessible from other Durable Objects. | ||
|
|
||
| Storage API includes key-value (KV) API, SQL API, and point-in-time-recovery (PITR) API. | ||
| Storage API includes key-value (KV) API, SQL API, and point-in-time-recovery (PITR) API. | ||
|
|
||
| - Durable Object classes with the key-value storage backend can use KV API. | ||
| - Durable Object classes with the SQLite storage backend can use KV API, SQL API, and PITR API. | ||
| - Durable Object classes with the key-value storage backend can use KV API. | ||
| - Durable Object classes with the SQLite storage backend can use KV API, SQL API, and PITR API. | ||
|
|
||
| - term: "KV API" | ||
| general_definition: |- | ||
| API methods part of Storage API that support persisting key-value data. | ||
| - term: "KV API" | ||
| general_definition: |- | ||
| API methods part of Storage API that support persisting key-value data. | ||
|
|
||
| - term: "SQL API" | ||
| general_definition: |- | ||
| API methods part of Storage API that support SQL querying. | ||
| - term: "SQL API" | ||
| general_definition: |- | ||
| API methods part of Storage API that support SQL querying. | ||
|
|
||
| - term: Migration | ||
| general_definition: |- | ||
| A Durable Object migration is a mapping process from a class name to a runtime state. | ||
| Initiate a Durable Object migration when you need to: | ||
| - term: Migration | ||
| general_definition: |- | ||
| A Durable Object migration is a mapping process from a class name to a runtime state. | ||
| Initiate a Durable Object migration when you need to: | ||
|
|
||
| - Create a new Durable Object class. | ||
| - Rename a Durable Object class. | ||
| - Delete a Durable Object class. | ||
| - Transfer an existing Durable Objects class. | ||
| - Create a new Durable Object class. | ||
| - Rename a Durable Object class. | ||
| - Delete a Durable Object class. | ||
| - Transfer an existing Durable Objects class. | ||
|
|
||
| - term: Alarm | ||
| general_definition: |- | ||
| A Durable Object alarm is a mechanism that allows you to schedule the Durable Object to be woken up at a time in the future. | ||
| - term: Alarm | ||
| general_definition: |- | ||
| A Durable Object alarm is a mechanism that allows you to schedule the Durable Object to be woken up at a time in the future. |
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
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.