Skip to content

story: Fix tree story in web gallery - #2363

Merged
huacnlee merged 1 commit into
longbridge:mainfrom
lurenjia534:main
May 13, 2026
Merged

story: Fix tree story in web gallery#2363
huacnlee merged 1 commit into
longbridge:mainfrom
lurenjia534:main

Conversation

@lurenjia534

Copy link
Copy Markdown
Contributor

Closes #2139

Description

Fixes the Tree story in the web gallery by avoiding filesystem reads in the WASM target.

The native story still builds the tree from the local working directory, while the web gallery now uses static example tree data. This keeps the desktop behavior unchanged and makes the Tree example render correctly in the browser, where local filesystem access is unavailable.

Screenshot

Before After
Before After

How to Test

cargo check -p gpui-component-story
cargo clippy -p gpui-component-story -- -D warnings
RUSTUP_TOOLCHAIN=nightly cargo check -p gpui-component-story-web --target wasm32-unknown-unknown
cargo test -p gpui-component-story
cargo test -p gpui-component tree::tests

Manual web verification:

cd crates/story-web
RUSTUP_TOOLCHAIN=nightly make dev

Open the local gallery URL, search for tree, and verify the Tree story displays a file tree and supports selection/expand behavior.

Checklist

  • I have read the CONTRIBUTING document and followed the guidelines.
  • Reviewed the changes in this PR and confirmed AI generated code (If any) is accurate.
  • Passed cargo run for story tests related to the changes.
  • Tested macOS, Windows and Linux platforms performance (if the change is platform-specific)

@huacnlee
huacnlee merged commit 764b26e into longbridge:main May 13, 2026
3 checks passed
@huacnlee

Copy link
Copy Markdown
Member

Thanks

AzureZee pushed a commit to AzureZee/gpui-component that referenced this pull request May 16, 2026
Closes longbridge#2139

## Description

Fixes the Tree story in the web gallery by avoiding filesystem reads in
the WASM target.

The native story still builds the tree from the local working directory,
while the web gallery now uses static example tree data. This keeps the
desktop behavior unchanged and makes the Tree example render correctly
in the browser, where local filesystem access is unavailable.

## Screenshot

| Before | After |
| ------ | ----- |
| <img width="3840" height="2080" alt="Before"
src="https://github.com/user-attachments/assets/5e4c2861-469d-4a2e-a8b6-07fa9db7f116"
/> | <img width="3840" height="2080" alt="After"
src="https://github.com/user-attachments/assets/d5340448-e3b2-45ce-a0ee-132102c7ca9b"
/> |

## How to Test

```bash
cargo check -p gpui-component-story
cargo clippy -p gpui-component-story -- -D warnings
RUSTUP_TOOLCHAIN=nightly cargo check -p gpui-component-story-web --target wasm32-unknown-unknown
cargo test -p gpui-component-story
cargo test -p gpui-component tree::tests
```

Manual web verification:

```bash
cd crates/story-web
RUSTUP_TOOLCHAIN=nightly make dev
```

Open the local gallery URL, search for `tree`, and verify the Tree story
displays a file tree and supports selection/expand behavior.

## Checklist

- [x] I have read the [CONTRIBUTING](../CONTRIBUTING.md) document and
followed the guidelines.
- [x] Reviewed the changes in this PR and confirmed AI generated code
(If any) is accurate.
- [x] Passed `cargo run` for story tests related to the changes.
- [ ] Tested macOS, Windows and Linux platforms performance (if the
change is platform-specific)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tree component example in the web UI seems to be broken

2 participants