-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Fix semantic walker not firing exitOperation or exitModelProperty #4381
Conversation
All changed packages have been documented.
Show changes
|
You can try these changes here
|
@@ -229,6 +229,7 @@ function navigateOperationType(operation: Operation, context: NavigationContext) | |||
if (operation.sourceOperation) { | |||
navigateTypeInternal(operation.sourceOperation, context); | |||
} | |||
context.emit("exitOperation", operation); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the late comment - but I think the exit
methods still won't be executed if the pre-order callback sets no recursion. Maybe not a real issue if it's unlikely someone would use both pre and post-order callbacks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh I thought that was the expected behavior, but makes sense, I will follow up on this
namespaces: [] as Namespace[], | ||
operations: [] as Operation[], | ||
exitOperations: [] as Operation[], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any reason not to extend the post-order callbacks to every type? Looks like we might still be missing some like namespaces
, interfaces
, etc.
Fix: #4379