Extract vendored dioxus-primitives components into their own crate #10
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-extract-dx-components"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
crates/web/src/components/(badge, button, input, scroll_area, separator, sheet, sidebar, skeleton, tooltip) was a byte-for-byte copy of the DioxusLabs/componentspreview/registry — a shadcn-style "copy this source into your project" set, not something published as a real crate dependency.feedsignal-dioxus-componentsworkspace crate (crates/dioxus-components) so it reads as vendored code the app depends on, not application source.crates/webnow importsfeedsignal_dioxus_components::{badge, button, input, scroll_area, sidebar}instead ofcrate::components::*.css_modulepaths were touched. Going forward, app-specific styling should layer on via theclass/attributesprops each component already accepts rather than editing the vendored files directly.Test plan
cargo check -p feedsignal-dioxus-componentscargo check -p feedsignal-web --no-default-features --features webcargo check -p feedsignal-web --no-default-features --features servercargo fmt --checkcargo clippy --workspace --exclude feedsignal-web --all-targets -- -D warningscargo clippy -p feedsignal-web --no-default-features --features server --all-targets -- -D warningscargo clippy -p feedsignal-web --no-default-features --features web --target wasm32-unknown-unknown -- -D warningscargo test --workspace --exclude feedsignal-web🤖 Generated with Claude Code
WIP: Extract vendored dioxus-primitives components into their own crateto Extract vendored dioxus-primitives components into their own crate