-
Notifications
You must be signed in to change notification settings - Fork 58
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
Support ip route get
#86
base: main
Are you sure you want to change the base?
Conversation
Any idea bout the status f this PR? |
Seems the maintainer has been inactive for some time on this repo, so we have to either wait or fork. |
not sure if valuable - but as an alternate to adding a dump variable at construction time I thought it might make sense to drive this behavior by the presence of a destination attribute. If destination attribute was added (as one would have to to obtain a route) user is looking for a single route
edit: slightly cleaner version of ^^
|
My rust is not so great - so I wasn't able to use your fix - so you have an example of how you would modify the existing examples? Reading your commit message I tried this but
yielding
Feels like one would need to add an access method, might just make my own temporary for till that clears up as the solution I outlined in the prior comment works transparently |
7db34e9
to
570b762
Compare
Oops, seems like I somehow missed
This definitely seems feasible! I wonder if there are corner cases, though. I will integrate your changes and mention you in the commit message when I am less busy (or create a new PR superseding this one) :) |
if you do please note i updated my comment with slightly cleaner code |
…specified We can have the behaviour of `ip route get` now. Co-Developed-By: Nevo Hed <[email protected]>
570b762
to
e4193d3
Compare
Rework of #23. Only adds
RouteGetRequest::dump
option, where specifyingreq.dump(false)
will mimic the behaviour ofip route get
, and replacingimpl TryStream
withimpl Stream<Item = Result<...>>
. There is no breaking change.