Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bug: Cannot use ReadOnlySignal as a prop when using the #[component] macro #1979

Closed
marc2332 opened this issue Feb 25, 2024 · 0 comments
Closed

bug: Cannot use ReadOnlySignal as a prop when using the #[component] macro #1979

marc2332 opened this issue Feb 25, 2024 · 0 comments
Assignees
@jkelleyrtp
Milestone
0.5.0: Signals

Comments

@marc2332
Copy link
Contributor

Problem

Cannot use ReadOnlySignal as a prop when using the #[component] macro

Expected behavior

Work

Screenshots

image

image

Environment:

  • Dioxus version: main
  • Rust version: 1.75
  • OS info: Windows
  • App platform: Freya
@jkelleyrtp jkelleyrtp added this to the 0.5.0: Signals milestone Mar 7, 2024
@jkelleyrtp jkelleyrtp self-assigned this Mar 8, 2024
jkelleyrtp added a commit that referenced this issue Mar 8, 2024
@jkelleyrtp
fix #1979: generated Owned impl for the props builder was using the w…
76c5c2c 
…rong generics.

This commit fixes the owned impl to use the original generics rather than the build generics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jkelleyrtp jkelleyrtp

Labels
None yet
Projects
None yet
Milestone
0.5.0: Signals
Development

No branches or pull requests
2 participants
@jkelleyrtp @marc2332