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.

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

The future of reactive #32

Open
codyduong opened this issue Aug 10, 2024 · 2 comments
Open

The future of reactive #32

codyduong opened this issue Aug 10, 2024 · 2 comments
Assignees
Labels
question Further information is requested
Milestone

Comments

@codyduong
Copy link
Owner

Discussion for reactive. Initially I wanted every prop accept reactive, but this might be overkill.

Instead in lieu maybe accept the following

  • Clock.format
  • Label.label
  • Base.class
@codyduong codyduong added the question Further information is requested label Aug 10, 2024
@codyduong codyduong self-assigned this Aug 10, 2024
@codyduong
Copy link
Owner Author

On a further note, it would be best for values that are NonOptions, aka required fields only.

@codyduong codyduong added this to the 0.2.0 milestone Aug 10, 2024
@codyduong codyduong mentioned this issue Aug 11, 2024
Merged
@codyduong
Copy link
Owner Author

Reactive still has issues on fields which are not regularly watched (ie. if it is not already constructed in a relm4 view! macro with watcher, it will be hard to watch the ArcMutex for updates. So it serves no purpose in custom widgets)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant