-
Notifications
You must be signed in to change notification settings - Fork 568
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
Add example to ViewSwitcher #1822
Conversation
I have been thinking and talking about this here And it is maybe worth considering that a proper documenting strategy should be born. Tbh, even though it's kind of common sense, as per Rust's guidelines, I think the current PR fails |
Did you reach a conclusion about this? FWIW, I don't think it's necessary to have a |
There has been no feedback to date. And so it's kind of stuck. |
Well in that case I suggest we just merge it. Having an example is clearly better than not having one, so there's no point in being stuck on it. Any objections? (edited to add: if there aren't any by tomorrow, I'll merge it) |
the example should be in top level docs of |
Good question. I wanted it in `new()` because that's when I need to be
reminded of the order of the parameters in the closures.
…On Wed, 16 Jun 2021, 05:59 Manmeet Maan, ***@***.***> wrote:
the example should be in top level docs of ViewSwitcher not
ViewSwitcher::new?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR4WFRITN7V34BNHADEMALTTAOTFANCNFSM46HW7GSA>
.
|
Merging, as no objections |
Let me know if you don't like it, I should modify anything? I'm hoping to add examples to many more areas of Druid that could benefit from them.