Skip to content

Conversation

@mendonk
Copy link
Collaborator

@mendonk mendonk commented Aug 19, 2025

Issue #9343 mentions that __init__.py is required for Langflow to detect custom components, and the docs examples don't include this. This PR adds them, and a troubleshooting entry for other users who might see this issue.

Summary by CodeRabbit

  • Documentation
    • Updated documentation for custom components in Langflow
    • Added troubleshooting guide for custom components not appearing in the visual editor
    • Clarified directory structure requirements for component development
    • Provided guidance on resolving component loading issues

@mendonk mendonk self-assigned this Aug 19, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 19, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request updates documentation for Langflow's custom components, focusing on clarifying directory structure requirements, specifically emphasizing the need for an __init__.py file in category directories and providing troubleshooting guidance for component loading issues.

Changes

Cohort / File(s) Change Summary
Documentation Updates, docs/docs/Components/components-custom-components.mdx, docs/docs/Support/troubleshooting.mdx Added detailed instructions for custom component directory structure, emphasizing the requirement of __init__.py files in category directories

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly Related PRs

Suggested Labels

size:M, lgtm

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs-custom-component-init-dir

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 19, 2025
@mendonk mendonk changed the title docs: custom component directory requires an __init__.py file docs: custom component directory requires an init.py file Aug 19, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 19, 2025
@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 19, 2025
Copy link
Contributor

@Victor-w-Madeira Victor-w-Madeira left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions github-actions bot added the lgtm This PR has been approved by a maintainer label Aug 19, 2025
@github-actions github-actions bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 21, 2025
@sonarqubecloud
Copy link

@github-actions
Copy link
Contributor

github-actions bot commented Aug 21, 2025

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

@mendonk mendonk added this pull request to the merge queue Aug 21, 2025
Merged via the queue into main with commit 5099ffc Aug 21, 2025
16 checks passed
@mendonk mendonk deleted the docs-custom-component-init-dir branch August 21, 2025 17:02
lucaseduoli pushed a commit that referenced this pull request Aug 22, 2025
* add-init-py-to-examples

* add-troubleshooting

* remove-extra-comment
lucaseduoli pushed a commit that referenced this pull request Aug 25, 2025
* add-init-py-to-examples

* add-troubleshooting

* remove-extra-comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants