Skip to content

chore(docs): remove remaining yml references from docs #1492

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.

Sign up for GitHub

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
waleedlatif1 merged 1 commit into from
Sep 30, 2025
Merged

chore(docs): remove remaining yml references from docs #1492

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 1 addition & 27 deletions apps/docs/content/docs/en/blocks/agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,33 +175,7 @@ Use a `Memory` block with a consistent `id` (for example, `chat`) to persist mes
- Read the conversation history for context
- Append the Agent's reply after it runs

```yaml
# 1) Add latest user message
- Memory (operation: add)
id: chat
role: user
content: {{input}}

# 2) Load conversation history
- Memory (operation: get)
id: chat

# 3) Run the agent with prior messages available
- Agent
System Prompt: ...
User Prompt: |
Use the conversation so far:
{{memory_get.memories}}
Current user message: {{input}}

# 4) Store the agent reply
- Memory (operation: add)
id: chat
role: assistant
content: {{agent.content}}
```

See the `Memory` block reference for details: [/tools/memory](/tools/memory).
See the [`Memory`](/tools/memory) block reference for details.

## Inputs and Outputs

Expand Down
8 changes: 0 additions & 8 deletions apps/docs/content/docs/en/triggers/api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,14 +24,6 @@ The API trigger exposes your workflow as a secure HTTP endpoint. Send JSON data

Add an **Input Format** field for each parameter. Runtime output keys mirror the schema and are also available under `<api.input>`.

```yaml
- type: string
name: userId
value: demo-user # optional manual test value
- type: number
name: maxTokens
```

Manual runs in the editor use the `value` column so you can test without sending a request. During execution the resolver populates both `<api.userId>` and `<api.input.userId>`.
Comment on lines 25 to 27
Copy link
Contributor

@greptile-apps greptile-apps bot Sep 30, 2025

Choose a reason for hiding this comment

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

style: After removing the YAML example, the text references specific field names (userId, maxTokens) that were only shown in the removed code block. Consider adding a brief inline example or updating the text to use generic field names for clarity.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: apps/docs/content/docs/en/triggers/api.mdx
Line: 25:27

Comment:
style: After removing the YAML example, the text references specific field names (`userId`, `maxTokens`) that were only shown in the removed code block. Consider adding a brief inline example or updating the text to use generic field names for clarity.

How can I resolve this? If you propose a fix, please make it concise.


## Request Example
Expand Down
238 changes: 0 additions & 238 deletions apps/docs/content/docs/en/yaml/block-reference.mdx
View file
Open in desktop

This file was deleted.

Loading