docs/docs.json (2)

271-280: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Navigation inconsistency: creating-workers/channels in nav but not featured in index page cards.

The "Creating Workers" navigation includes creating-workers/channels (line 278), but according to the relevant code snippet from creating-workers/index.mdx, the landing page only features three navigation cards: Workers, Triggers, and Functions. This creates an inconsistency where Channels is accessible via navigation but not featured prominently on the section's landing page.

Please either:

1. Add a Channels card to creating-workers/index.mdx to maintain consistency, or
2. Add a note explaining why Channels is available but not featured (e.g., "Additional topics: Channels")

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/docs.json` around lines 271 - 280, The "Creating Workers" nav lists
creating-workers/channels but the creating-workers/index.mdx landing page only
shows cards for Workers, Triggers, and Functions; fix by either adding a
Channels card to creating-workers/index.mdx that links to
creating-workers/channels (match styling/metadata of the existing cards: title
"Channels", description, and href "creating-workers/channels") or add a short
explanatory note on creating-workers/index.mdx (e.g., "Additional topics:
Channels" with a link to creating-workers/channels) so the navigation and
landing page are consistent.

---

250-261: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix “Channels” discoverability in the Creating Workers docs

• docs/using-iii/channels.mdx is not present, so there’s no orphaned page to restore under “Using iii”.
• docs/docs.json includes creating-workers/channels in the 0.13.x “Creating Workers” nav, but docs/creating-workers/index.mdx only renders cards for Workers/Triggers/Functions—add a “Channels” card (or adjust the layout to include it) to match navigation.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/docs.json` around lines 250 - 261, The navigation references a missing
"creating-workers/channels" page and the Creating Workers landing
(docs/creating-workers/index.mdx) doesn't show a Channels card to match
docs/docs.json; either add a Channels card to docs/creating-workers/index.mdx
that links to creating-workers/channels (and ensure that target page exists or
is created), or remove the "creating-workers/channels" entry from
docs/docs.json; update the Creating Workers component where
Worker/Trigger/Function cards are rendered (search for
docs/creating-workers/index.mdx and the card component or array) to include a
Channels entry (title "Channels", description, and href
"creating-workers/channels") so nav and page are consistent.

docs/using-iii/triggers.mdx (2)

37-44: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Validate III_URL in the Python example for consistency.

The Node/TypeScript example (lines 23-24) and Rust example (line 61) both explicitly validate that III_URL is set before proceeding. The Python example should follow the same pattern to provide clear error feedback and maintain consistency across languages.

🐍 Proposed fix to add III_URL validation

 import os
 from iii import register_worker, InitOptions, TriggerAction
 
+url = os.environ.get("III_URL")
+if not url:
+    raise ValueError("III_URL must be set")
+
 worker = register_worker(
-    os.environ.get("III_URL"),
+    url,
     InitOptions(worker_name="caller"),
 )

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/using-iii/triggers.mdx` around lines 37 - 44, The Python snippet
currently calls register_worker(...) without confirming III_URL is set; add an
explicit validation before calling register_worker: read III_URL from the
environment (e.g., os.environ.get or os.getenv) into a variable, check if it's
falsy, and raise a clear exception or exit (ValueError or SystemExit) with a
message like "III_URL must be set" so register_worker(...) is only invoked when
III_URL is present; update the code surrounding register_worker, InitOptions,
and TriggerAction accordingly.

---

138-145: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Validate III_URL in the Python registration example.

Similar to the earlier "Call a function directly" section, this Python example should validate III_URL before use to match the Node/TypeScript (lines 125-126) and Rust (line 160) examples.

🐍 Proposed fix to add III_URL validation

 import os
 from iii import register_worker, InitOptions
 
+url = os.environ.get("III_URL")
+if not url:
+    raise ValueError("III_URL must be set")
+
 worker = register_worker(
-    os.environ.get("III_URL"),
+    url,
     InitOptions(worker_name="my-worker"),
 )

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/using-iii/triggers.mdx` around lines 138 - 145, The example uses
os.environ.get("III_URL") without validating it; update the registration snippet
to read and validate the III_URL environment variable before calling
register_worker (e.g., retrieve os.environ.get("III_URL") into a variable, check
if it's truthy/raise an informative exception or print/log and exit if missing),
then pass that validated variable into register_worker along with
InitOptions(worker_name="my-worker") so register_worker and InitOptions are only
called when III_URL is present.