-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
hot.accept tap interceptor returns T/F based on the number of args #6962
Conversation
For the test case, create a folder named
You can run the hot test suite using:
|
If you returns For single argument parser.walkExpression(expr.arguments[1]); // other args are ignored
return true; |
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.
See my comments
@justinhelmer Thanks for your update. I labeled the Pull Request so reviewers will review it again. @ooflorent Please review the new changes. |
@ooflorent - sorry for the delay on this. I was following the original issue thread and missed your comments. One thing to note for others reading this thread - tests must be in a subdirectory of
as opposed to:
Then, after familiarizing myself with the existing test patterns and your comments, I was able to get it working. I have pushed the changes for final review. Now the question remains - in order to resolve #6919 - I need to make a similar change to the |
I squashed into the original commit which is why I cannot resolve the requested change. |
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Thanks |
@sokra @ooflorent - what about wp3? (per #6919) |
Could you submit a PR for the v3 branch? |
@ooflorent - I would love to, but am currently blocked. Awaiting feedback from someone who is knowledgeable of the system. Please see my most recent two comments on #6919 |
addresses #6919
What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
yes
If relevant, link to documentation update:
N/A
Summary
#6919
Does this PR introduce a breaking change?
Not to any external interface