feat(routing): add Print method to RouteLookup for route inspection #3835
+64
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
👍🏽 |
Member
|
I don't think that this is needed for the purpose. |
Add Print method to RouteLookup struct that returns a formatted string representation of valid routes from the captured routing table. This enables debugging and inspection of the current routing state. Since library users can't access routing table info, this can give nive view only access and to compare against ekip to validate routes. Signed-off-by: Mustafa Abdelrahman <[email protected]>
MustafaSaber
force-pushed
the
print-valid-rt
branch
from
467a48b to
8d81f5e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Print method to RouteLookup struct that returns a formatted string representation of valid routes from the captured routing table. This enables debugging and inspection of the current routing state. Since library users can't access routing table info, this can give nive view only access and to compare against ekip to validate routes.