You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem this feature solves
Similar to #400, the MRC builder knows the names of both nodes the edge is connecting to and could easily construct a string like "/seg1/A <-- /seg1/B" and supply it to the edge at construction time.
This would allow for easier debugging in MRC.
Describe your ideal solution
Ideally Builder would pass in the name of both nodes to the EdgeBuilder, this way both EdgeHolders will know the name of the node they're a holder for, and the edge would know the names of both nodes.
This way all three classes can override the << operator and print some meaningful information to the console and/or would have some identifying attributes visible in the debugger.
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
I agree to follow MRC's Code of Conduct
I have searched the open feature requests and have found no duplicates for this feature request
The text was updated successfully, but these errors were encountered:
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem this feature solves
Similar to #400, the MRC builder knows the names of both nodes the edge is connecting to and could easily construct a string like "/seg1/A <-- /seg1/B" and supply it to the edge at construction time.
This would allow for easier debugging in MRC.
Describe your ideal solution
Ideally Builder would pass in the name of both nodes to the EdgeBuilder, this way both EdgeHolders will know the name of the node they're a holder for, and the edge would know the names of both nodes.
This way all three classes can override the << operator and print some meaningful information to the console and/or would have some identifying attributes visible in the debugger.
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: