-
Notifications
You must be signed in to change notification settings - Fork 14
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
DC Branch Support #148
DC Branch Support #148
Conversation
@bknueven I just blindly took any code that dealt with branch elements and included dc_branch elements as well. I don't know if that was always the right thing to do, and as a result this PR is marked as WIP. Feel free to take off the WIP status after you've reviewed it if you feel OK about where I added DC support. Most of the changes boiled down to looping over two sets of elements instead of just one. Wherever there used to be for loops over branch elements, I leaned toward including both kinds of branches in a single loop rather than copying the code into a second loop. Also, I added a couple of TODO comments I hope you'll notice and resolve. |
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 a few minor comments
Co-authored-by: bknueven <[email protected]>
Co-authored-by: bknueven <[email protected]>
Co-authored-by: bknueven <[email protected]>
Co-authored-by: bknueven <[email protected]>
Since we just added support for dc_branch elements in the Egret GMLC parser, we want to be sure Prescient includes DC branches in its logic and reporting.