Skip to content
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

feat: Validate that a generic node is not dangling #998

Merged

Conversation

aababilov
Copy link
Collaborator

A dangling node has just one incident location in the pathway graph.
Such generic node is useless because there is no benefit in visiting it.

A dangling node has just one incident location in the pathway graph.
Such generic node is useless because there is no benefit in visiting it.
@aababilov aababilov force-pushed the PathwayDanglingGenericNodeValidator branch from a80c30c to 100f818 Compare September 2, 2021 13:13
@aababilov
Copy link
Collaborator Author

I had to resolve a merge conflict in RULES.md and I also updated NOTICES.md which will lead to another merge conflict with another PR. We really need to do something with that.

Copy link
Contributor

@isabelle-dr isabelle-dr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for updating the documentation!

@aababilov
Copy link
Collaborator Author

Thanks for review!

@aababilov aababilov merged commit 4941244 into MobilityData:master Sep 2, 2021
@isabelle-dr isabelle-dr mentioned this pull request Oct 28, 2021
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants