docs: move smart filter to be alphabetical

[mendonk]

Looks like the component name was changed in this commit
Move it to be alphabetical in the breadcrumb trail.

Summary by CodeRabbit

• Documentation
  • Relocated the documentation section for the Smart function component within the processing components guide. No content changes were made.

[coderabbitai]

Walkthrough

The documentation for the Smart function component was moved from one section to another within the same markdown file. The content itself was not altered; only its position in the document changed.

Changes

File(s)	Change Summary
docs/docs/Components/components-processing.md	Relocated the Smart function documentation section to a later point in the file; content unchanged.

Possibly related PRs

• fix: change lambda filter to smart function #8558: Refactors and renames the Lambda filter component to Smart function, updating related code and documentation, which connects to the documentation relocation in this PR.

Suggested labels

documentation, size:XS, lgtm

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch docs-move-lambda-function

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/docs/Components/components-processing.md (2)

483-483: Add descriptive alt text to image.
The image in the Smart function section (/img/component-lambda-filter.png) currently has an empty alt attribute, triggering MD045. Please provide meaningful alt text, for example:

- ![](/img/component-lambda-filter.png)
+ ![Smart function example output](/img/component-lambda-filter.png)

---

489-489: Use headings instead of emphasis for Inputs/Outputs.
The details panel uses bold emphasis (**Inputs** and **Outputs**), which linting flags as MD036. Consider converting these lines to proper subheadings for clarity and consistency:

- **Inputs**
+ #### Inputs

- **Outputs**
+ #### Outputs

Also applies to: 499-499

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 332738a and b4af5ac.

📒 Files selected for processing (1)

• docs/docs/Components/components-processing.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

docs/docs/Components/components-processing.md

484-484: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

489-489: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

499-499: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build-and-deploy

🔇 Additional comments (1)

docs/docs/Components/components-processing.md (1)

474-475: Section correctly placed alphabetically.
The Smart function section is now positioned between Save to File and Split text, which aligns with the intended alphabetical ordering of processing components.

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft