Community
Participate
Working Groups
Hello, I am running Tigerstripe 0.6.935.201102010903. I think there is a bug in the way the relations are displayed in the explorer. In fact, there are all displayed wrongly. I checked the “Show Relationship Anchors” in the Preferences/Tigerstripe/Explorer. I have an association artifact “AlarmHasTrackingRecords” between ResourceAlarm Entity and TrackingRecord Entity, the aEnd name is alarm of type ResourceAlarm, the zEnd anme is trackingRecord of type TrackingRecord . It is navigable from ResourceAlarm to TrackingRecord, so only the end TrackingRecord is checked as navigable. Tigerstripe is showing in the explorer: alarm:TrackingRecord (AlarmHasTrackingRecord), so giving it the name of the end on the ResourceAlarm side while I would expect to get trackingRecord:TrackingRecord (AlarmHasTrackingRecord). RSM for instance is displaying the roles (a/z end) in the order corresponding to what would be expected. I used this example but this is valid for all associations. This is quite annoying and limits the use of the relationship anchors. Best regards, Marc
Created attachment 203791 [details] Attaching snapshot to clarify what Marc is suggesting Attaching snapshot to clarify what Marc is suggesting. I think what Marc is suggesting makes sense. Need to communicate this with our modeling team to make sure they're on the same page.
I agree with Marc e.g. under Resource Alarm, I'll see trackingRecord:TrackingRecord under TrackingRecord, I'll see alarm:ResourceAlarm
Thanks for the snapshot, it illustrates perfectly my point. and thanks for supporting the case.
fixed
Marking as fixed.
Verified. Thanks!
