-
Notifications
You must be signed in to change notification settings - Fork 0
Traverse Action
Leon Starr edited this page Jul 10, 2025
·
5 revisions
We'll keep track of our hops as we process the Path_a component, populating them as we go into the metamodel.
We also set a class_cursor to track which class is currently providing the instance set to hop from.
And we initialize a string, name, which we'll use to uniquely identify our traverse action.
We check to ensure the path length has at least two hop elements, otherwise we can't hop anywhere.
Also we ensure that the destination class exists in our model.
Copyright 2022, 2023, 2025 © Leon Starr under MIT Open Source License