-
Notifications
You must be signed in to change notification settings - Fork 567
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
adding added controller widget #1485
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I had some minor nitpicks with the docs.
} | ||
|
||
impl<T: Data> Added<T> { | ||
/// Create a new [`Controller`] widget to respond to widget added to tree event. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Splitting hairs, maybe, but a Controller
isn't a widget (the ControllerHost
is).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I was following the Click
widget example. I don't remember if that's a full widget or a Controller type. So most of the docs I've written is paraphrasing Click
's docs. I was trying to be consistent with that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know what would be preferred here. I'm leaving it as is. I think calling it a Controller widget is appropriate. Anything else might be too verbose. I guess you can just call it controller like, "Create a new controller to respond to widget added to tree event".
Looks good to me! Unfortunately, clippy broke the build again and we can't merge until its fixed. I'll try to get to it later today if no one beats me to it. |
I've fixed up clippy for the rust 1.49 in #1461. If you rebase on that after it's merged, the clippy warning should go away. :) Update You can rebase now to get the clippy fixes. If you need any help rebasing ping me; I'm happy to help. 😄 |
Hi, I see the label waiting on author. Is there something I'm supposed to do? |
You'll need to rebase your branch onto the master branch, to pull in the fixes for the broken CI. |
Uhh did I rebase correctly? |
Rebasing is fiddly! I will check out the PR and fix it up when I get chance. |
it looks like something went a bit wrong and you brought in a bunch of old commits. I would just do |
Am i doing this from the current state? Edit: Ok that should be right, now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just skimming this again: I have a few little doc tweaks, but I also have one larger question, which is whether or not we should also be passing in the widget itself to the closure, as like &mut W
? I think this probably makes sense.
Co-authored-by: Colin Rofls <[email protected]>
Co-authored-by: Colin Rofls <[email protected]>
Yep squash sounds good :) |
I had an issue with the documentation display. I followed the
Click
widget as an example, but I don't think the documentation is showing up as expected. Also there seems to be extra'
in theClick
widget documentation. Is there anything I missed in the implementation?EDIT (Richard Dodd) Closes #1480.