diff --git a/nexus-sdk/guides/dag-construction.md b/nexus-sdk/guides/dag-construction.md index 522c7ef..eced845 100644 --- a/nexus-sdk/guides/dag-construction.md +++ b/nexus-sdk/guides/dag-construction.md @@ -229,5 +229,5 @@ For working examples, see the following files in the `cli/src/dag/_dags` directo - `ig_story_planner_valid.json`: Example of a complex workflow - `entry_groups_valid.json`: Example of using entry groups. -For examples of invalid DAGs and common mistakes to avoid (especially regarding Rule 5 - Race Conditions), see the diagrams in [workflow documentation](../../nexus-next/packages/workflow.md) and the `*_invalid.json` files in the [testing DAG directory](https://github.com/Talus-Network/nexus-sdk/tree/v0.8.4/sdk/src/dag/_dags). +For examples of invalid DAGs and common mistakes to avoid (especially regarding Rule 5 - Race Conditions), see the diagrams in [workflow documentation](../../nexus-next/packages/workflow.md) and the `*_invalid.json` files in the [testing DAG directory](https://github.com/Talus-Network/nexus-sdk/tree/v1.0.0/sdk/src/dag/_dags). diff --git a/nexus-sdk/guides/math-branching-with-chat.md b/nexus-sdk/guides/math-branching-with-chat.md index f07ab6d..4f469e7 100644 --- a/nexus-sdk/guides/math-branching-with-chat.md +++ b/nexus-sdk/guides/math-branching-with-chat.md @@ -182,7 +182,7 @@ We can no longer assign outputs to be on the math tools because they now have ou "outputs": [ { "vertex": "chat_completion", - "output_variant": "ok", + "output_variant": "text", "output_port": "completion" } ] @@ -556,7 +556,7 @@ Here's the complete DAG definition that combines all the components we've discus "outputs": [ { "vertex": "chat_completion", - "output_variant": "ok", + "output_variant": "text", "output_port": "completion" } ] diff --git a/nexus-sdk/guides/setup.md b/nexus-sdk/guides/setup.md index 8b5a542..5042331 100644 --- a/nexus-sdk/guides/setup.md +++ b/nexus-sdk/guides/setup.md @@ -38,7 +38,7 @@ To install directly from the source using `cargo`, run: ```bash cargo install nexus-cli \ --git https://github.com/talus-network/nexus-sdk \ - --tag v0.8.4 \ + --tag v1.0.0 \ --locked ``` @@ -54,7 +54,7 @@ nexus --version {% tab title="Testnet" %} ```bash -wget -O ~/.nexus/objects.testnet.toml https://storage.googleapis.com/production-talus-sui-objects/v0.8.4/objects.testnet.toml +wget -O ~/.nexus/objects.testnet.toml https://storage.googleapis.com/production-talus-sui-objects/v1.0.0/objects.testnet.toml ``` {% endtab %} @@ -62,7 +62,7 @@ wget -O ~/.nexus/objects.testnet.toml https://storage.googleapis.com/production- {% tab title="Mainnet" %} ```bash -wget -O ~/.nexus/objects.mainnet.toml https://storage.googleapis.com/production-talus-sui-objects/v0.8.4/objects.mainnet.toml +wget -O ~/.nexus/objects.mainnet.toml https://storage.googleapis.com/production-talus-sui-objects/v1.0.0/objects.mainnet.toml ``` {% endtab %} diff --git a/nexus-sdk/tool-development.md b/nexus-sdk/tool-development.md index b62b261..8899f98 100644 --- a/nexus-sdk/tool-development.md +++ b/nexus-sdk/tool-development.md @@ -16,6 +16,10 @@ These guidelines are not meant to be technical specifications but rather a set o - ✅: `err`, `err_http` - ❌: `error`, `failure`, `http_exception` +### Erroneous Output Variants + +While not strictly required, it's a best practice to create a separate output variant for errors. Any output variant with the `err` prefix is treated as erroneous and handled differently by Nexus. Specifically, all ports in an error variant are automatically passed on-chain, regardless of whether edges or outputs are defined in the DAG. + ## Interface Design ### ... should be as generic as possible diff --git a/nexus-sdk/toolkit-rust.md b/nexus-sdk/toolkit-rust.md index d9854b4..bd9d840 100644 --- a/nexus-sdk/toolkit-rust.md +++ b/nexus-sdk/toolkit-rust.md @@ -15,7 +15,7 @@ Alternatively, you can add the following to your `Cargo.toml` file: ```toml [dependencies.nexus-toolkit] git = "https://github.com/Talus-Network/nexus-sdk" -tag = "v0.8.4" +tag = "v1.0.0" package = "nexus-toolkit" ```