-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
feat(picker): Add volume picker to CellPicker #2944
feat(picker): Add volume picker to CellPicker #2944
Conversation
CI is failing due to old node versions. I will update it. |
Ok. Thanks. I tried to make fewer changes so you can review effectively. Do you want me to create a video? |
If you have an example, that would be a great addition to demonstrate its capabilities. One note I had skimming your changes is that the package.json changes are irrelevant to the functionality at hand. If the build works then I'm fine with the upgrades. |
THey are irrelevant. I wrongly executed npm install --force, that s it. I will make a video an put in the comments |
is this PR related to #2885 ? |
That appears to be a separate effort that hasn't been updated. |
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.
It's not clear why you had to modify package.json / package-lock.json
Please update CellPicker documentation accordingly.
Can you guys help me in git? I think I am doing a mess here. I want to delete the modifications I did in the package.json files |
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.
Can you please also update index.d.ts files accordingly ?
You will be able to squash all your branch commits eventually (I personnally use |
Added the example. Something i noticed is why you guys do not use the clipLine information in the following lines...
|
Not sure what do you mean, we do use |
The t1 and t2 updated values that restricts the ray |
I see, looks like a bug indeed. t1 and t2 should be extracted from the returned value... |
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.
LGTM
CI is red because this PR has some tests still failing. Please run |
It looks like a test is hanging (that's why you do not see any failure) |
How do I solve this problem? |
Found the problem. It was a point picker function which not correspond with the changes in vtkPicker |
@finetjul I nned to do something else? I saw the PR was pulled out from merge queue, despite no conflict with the base branch |
Can you rebase locally onto an updated master to see if there are any conflicts? Github recently had operational issues, so I don't know if there is an actual conflict or if the merge queues are currently broken. |
@floryst Made the change. It had one commit out from the base branch, despite no warnings in this PR. Please try again... |
c55057d
to
c93a020
Compare
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.
LGTM
@finetjul I think the branch is ok right. It already passed theses tests? |
🎉 This PR is included in version 29.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Context
This PRs adds volume picker capabilities to Cellpicker Object. I recorded a video of the functionality working.
Gravando.2023-10-26.123920.mp4
Results
Changes
PR and Code Checklist
npm run reformat
to have correctly formatted codeTesting