Skip to content

docs(WARP): add crate overview section#11445

Open
okwn wants to merge 2 commits into
warpdotdev:masterfrom
okwn:contrib/warp/crate-overview
Open

docs(WARP): add crate overview section#11445
okwn wants to merge 2 commits into
warpdotdev:masterfrom
okwn:contrib/warp/crate-overview

Conversation

@okwn
Copy link
Copy Markdown

@okwn okwn commented May 20, 2026

Summary

Add a Crate Overview section to WARP.md listing key crates and their purposes:

  • ai, channel_versions, command, editor, graphql, http_client, http_server, ipc
  • warpui, warpui_core, warp_core, app, integration

For each crate: where it is located, what it does, and why it matters for contributors.

Why this matters

New contributors don't know where to start when looking at the codebase. A clear map of the crate architecture helps them find the right file faster.

Changes

  • Add Crate Overview table to WARP.md
  • Cover 13 key crates with location, purpose, and contribution notes

Validation

Read WARP.md Crate Overview section and verify all listed crates exist.

Risk/Compatibility

Documentation only. No code or API changes.


Closes #11349 (File tree view's recursive watcher re-walks large subtrees)

Add a Crate Overview section to WARP.md listing key crates and their
purposes: ai, channel_versions, command, editor, graphql, http_client,
http_server, ipc, warpui, warpui_core, warp_core, app, and integration.
@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented May 20, 2026

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @okwn on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 20, 2026

@okwn

This PR is not linked to an issue that is marked with ready-to-implement.

Issue-state enforcement details:

  • Associated same-repo issues checked: none

  • Required readiness label: ready-to-implement

To continue, link this PR to a same-repo issue such as Closes #123 in the PR description, and make sure that issue has ready-to-implement.

Powered by Oz

@github-actions github-actions Bot added the external-contributor Indicates that a PR has been opened by someone outside the Warp team. label May 20, 2026
Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

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

@okwn

This PR is not linked to an issue that is marked with ready-to-implement.

Issue-state enforcement details:

  • Associated same-repo issues checked: none

  • Required readiness label: ready-to-implement

To continue, link this PR to a same-repo issue such as Closes #123 in the PR description, and make sure that issue has ready-to-implement.

Powered by Oz

@okwn
Copy link
Copy Markdown
Author

okwn commented May 20, 2026

@cla-bot check

@cla-bot cla-bot Bot added the cla-signed label May 20, 2026
@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented May 20, 2026

The cla-bot has been summoned, and re-checked this pull request!

@cbeaulieu-gt
Copy link
Copy Markdown

@okwn The linked issue does not appear related to the pr itself

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

Labels

cla-signed external-contributor Indicates that a PR has been opened by someone outside the Warp team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

File tree view's recursive watcher re-walks large subtrees (e.g. AppData\Local\Temp) on every event → sustained high CPU on Windows

2 participants