DiffGraph: allow simultaneous edge and node removal#347
Merged
mpollmeier merged 1 commit intomasterfrom Sep 19, 2025
Merged
Conversation
Prior to this, if a user tried to delete a node and an adjacent edge at the same time, we would run into this: ``` scala.MatchError: flatgraph.DiffGraphBuilder$RemoveEdge@7bcbf3a8 (of class flatgraph.DiffGraphBuilder$RemoveEdge) at flatgraph.DiffGraphApplier.splitUpdate$$anonfun$2(DiffGraphApplier.scala:228) ~[io.joern.flatgraph-core_3-0.1.25.jar:0.1.25] ``` Which was because the condition was on the `case RemoveEdge` filtered out that case and there's no fallback `case _` or similar. This makes it explicit and adds a test.
itsacoderepo
approved these changes
Sep 19, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Prior to this, if a user tried to delete a node and an adjacent edge at
the same time, we would run into this:
Which was because the condition was on the
case RemoveEdgefilteredout that case and there's no fallback
case _or similar.This makes it explicit and adds a test.