-
Notifications
You must be signed in to change notification settings - Fork 69
Make sweep tests more point-and-click like and clean up pathToNode retrieval #6963
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
base: main
Are you sure you want to change the base?
Make sweep tests more point-and-click like and clean up pathToNode retrieval #6963
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
const pathNodePath = getNodePathFromSourceRange( | ||
ast, | ||
path.graphSelections[0].codeRef.range | ||
) | ||
// Find the path declaration for the labeled argument | ||
const pathDeclaration = getNodeFromPath<VariableDeclaration>( | ||
ast, | ||
pathNodePath, | ||
path.graphSelections[0].codeRef.pathToNode, |
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.
@Irev-Dev @jtran I was playing with this as I remember you telling me to start trusting codeRef.pathToNode more. This change away from getNodePathFromSourceRange
works perfectly for me when I'm creating a sweep, but not if I'm editing one. Just a data point, I can help investigate whenever
Related https://github.com/KittyCAD/modeling-app/pull/6737/files#r2077656349
…-picking-the-wrong-profile-variable
…-picking-the-wrong-profile-variable
Relates to #6952
Part of #6650.