Skip to content

docs: fix critical inaccuracies in English documentation - #1512

Merged
lukegalbraithrussell merged 3 commits into
mainfrom
docs-clenaup
May 29, 2026
Merged

docs: fix critical inaccuracies in English documentation#1512
lukegalbraithrussell merged 3 commits into
mainfrom
docs-clenaup

Conversation

@lukegalbraithrussell

@lukegalbraithrusselllukegalbraithrussell commented May 28, 2026

Copy link
Copy Markdown
Contributor

Summary

🤖 Generated with Claude Code

Audited docs/english/ for accuracy against the source code and fixed critical issues (syntax errors, non-existent APIs, wrong language commands).

FileFix
experiments.mdRemoved entirely fictional BoltAgent/AsyncBoltAgent feature that never shipped; noted no active experiments
concepts/view-submissions.mdexcept e:except Exception as e: (SyntaxError)
concepts/message-sending.mdFixed unclosed string literal (SyntaxError); corrected say_stream null-condition wording
concepts/adding-agent-features.mdRemoved await from sync def functions (2 SyntaxErrors); fixed say_stream null-condition
concepts/updating-pushing-views.mdFixed corrupted views_open URL
concepts/using-the-assistant-class.mdCustom store requires find+save not get+save; setTitleset_title, setStatusset_status; "array"→"list"
tutorial/custom-steps.mdFixed invalid JSON ({}[] for required); added missing client param; complete outputs are optional
tutorial/custom-steps-workflow-builder-new/npm install/npm start → Python equivalents
tutorial/custom-steps-workflow-builder-existing/package.jsonrequirements.txt; removed invalid message= param; fixed f-string syntax for Python <3.12

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@lukegalbraithrussell
lukegalbraithrussell requested a review from a team as a code ownerMay 28, 2026 22:19
Once in VSCode, open the terminal. Let's install our package dependencies: run the following command(s) in the terminal inside VSCode:

```sh
npm install

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oopssssss

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lukegalbraithrussell A fix is great to find! Thanks! 📚 ✨

📺 thought: We might want to prefer steps using the CLI in ongoing iteration but not a blocker for this!

Comment threaddocs/english/experiments.md Outdated
Co-authored-by: Luke Russell <31357343+lukegalbraithrussell@users.noreply.github.com>
@codecov

codecovBot commented May 28, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.30%. Comparing base (df29f83) to head (aa1bbd1).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@ Coverage Diff @@## main #1512 +/- ##
=======================================
Coverage 91.30% 91.30% =======================================
Files 228 228 Lines 7271 7271 =======================================
Hits 6639 6639 Misses 632 632 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@zimegzimeg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad to read these improvements - thanks for a good eye 👁️‍🗨️

The one note I write is about CLI support but this is adjacent to what this PR intends so please ignore it. I'm also uncertain of the best practice for exceptions FWIW!

| `recipient_user_id` | Sourced from the `user_id` of the event.

If neither a `channel_id` or `thread_ts` can be sourced, then the utility will be `None`.
If either `channel_id` or `thread_ts` cannot be sourced, the utility will be `None`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 praise: Single truths are simple for me to follow thanks!

Once in VSCode, open the terminal. Let's install our package dependencies: run the following command(s) in the terminal inside VSCode:

```sh
npm install

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lukegalbraithrussell A fix is great to find! Thanks! 📚 ✨

📺 thought: We might want to prefer steps using the CLI in ongoing iteration but not a blocker for this!

```py
@app.function("sample_step")
def handle_sample_step_event(inputs: dict, fail: Fail, complete: Complete,logger: logging.Logger):
def handle_sample_step_event(client: WebClient, inputs: dict, fail: Fail, complete: Complete,logger: logging.Logger):

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🦠 praise: Thanks for catching this much!

------|------------
`client` | A `WebClient` instance used to make things happen in Slack. From sending messages to opening modals, `client` makes it all happen. For a full list of available methods, refer to the [Web API methods](/reference/methods). Read more about the `WebClient` for Bolt Python [here](https://docs.slack.dev/tools/bolt-python/concepts/web-api/).
`complete` | A utility method that invokes `functions.completeSuccess`. This method indicates to Slack that a step has completed successfully without issue. When called, `complete` requires you include an `outputs` object that matches your step definition in [`output_parameters`](#inputs-outputs).
`complete` | A utility method that invokes `functions.completeSuccess`. This method indicates to Slack that a step has completed successfully without issue. When called, `complete` accepts an optional `outputs` object that matches your step definition in [`output_parameters`](#inputs-outputs).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎁 praise: Thanks for catching this!

# Updating & pushing views

Modals contain a stack of views. When you call [`views_open`](https://api./reference/methods/views.open/slack.com/methods/views.open), you add the root view to the modal. After the initial call, you can dynamically update a view by calling [`views_update`](/reference/methods/views.update/), or stack a new view on top of the root view by calling [`views_push`](/reference/methods/views.push/)
Modals contain a stack of views. When you call [`views_open`](/reference/methods/views.open/), you add the root view to the modal. After the initial call, you can dynamically update a view by calling [`views_update`](/reference/methods/views.update/), or stack a new view on top of the root view by calling [`views_push`](/reference/methods/views.push/)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📚 praise: Fast load good I think!

@WilliamBergaminWilliamBergamin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice finds 💯

stream.append(markdown_text="Hello!")
stream.stop()
```
There are currently no active experiments. We're steadily staying stable.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean 🙏

@lukegalbraithrussell
lukegalbraithrussell merged commit e8222b5 into mainMay 29, 2026
16 checks passed
@lukegalbraithrussell
lukegalbraithrussell deleted the docs-clenaup branch May 29, 2026 15:40
@zimegzimeg added the docs Improvements or additions to documentation label Jun 30, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docsImprovements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@lukegalbraithrussell@zimeg@WilliamBergamin