You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps a corner case, but it threw me for a loop. This issue can be replicated using the DASC 2023 ingestion package. This dataset has SBVT_Result -[confirms]-> SBVT_Test. When path-finding is set to "predicate data", I can drag SBVT_Test onto the canvas, then drag SBVT_Result onto the canvas, and SemTK automatically connects them with confirms. This is the expected behavior.
When I use the parent classes, I don't get the same behavior. I drag TEST onto the canvas, then TEST_RESULT, but SemTK leaves them unconnected as if there are no trace between them in the dataset. This is misleading. However, if I drag TEST_RESULT first, then TEST, I get the dialog box to select confirms which is the behavior I expected.
The text was updated successfully, but these errors were encountered:
Perhaps a corner case, but it threw me for a loop. This issue can be replicated using the DASC 2023 ingestion package. This dataset has SBVT_Result -[confirms]-> SBVT_Test. When path-finding is set to "predicate data", I can drag SBVT_Test onto the canvas, then drag SBVT_Result onto the canvas, and SemTK automatically connects them with confirms. This is the expected behavior.
When I use the parent classes, I don't get the same behavior. I drag TEST onto the canvas, then TEST_RESULT, but SemTK leaves them unconnected as if there are no trace between them in the dataset. This is misleading. However, if I drag TEST_RESULT first, then TEST, I get the dialog box to select confirms which is the behavior I expected.
The text was updated successfully, but these errors were encountered: