Make link 'oneway' attribute optional when writing networks to disk #56
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.
See https://arupdigital.atlassian.net/browse/LAB-1002 and #55
Before this change
After this change
For discussion
1 - Although this fixes the bug, perhaps it does not go far enough? It feels like maybe we should validate the value of the
oneway
attribute (it must be'1'
) when it is present. Where would you do that?2 - It feels slightly odd that the validation happens at the point we try to write the network, rather than when we read the network in. I guess this is because the typical use case is to read the network, modify it in memory, then write out the new network? And we presumably want users to be able to read in "broken" networks, fix them, and then write them out?