fix(interactive): Fix Bugs of Property Loss of Edge Type After Type Inference #4032
Conversation
This file contains 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
Louyk14
previously approved these changes
Aug 13, 2024
BingqingLyu
previously approved these changes
Aug 13, 2024
…nto ir_fix_type_infer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What do these changes do?
When type inference has updated the edge type based on type constraints, it can result in the loss of all properties of the edge type. Consequently, a
property not existerror will be thrown when any subsequent operation attempts to access a property of the edge. This PR primarily addresses this issue.Related issue number
Fixes