-
Notifications
You must be signed in to change notification settings - Fork 24
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
Drag'n'drop hybrid import #4837
Conversation
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.
Backend is ready for review.
The frontend works, but there are some code questions left. See my comments below @philippotto
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.
Backend LGTM, I didn’t read the front-end code yet. A few thoughts to make sure everything works well:
- does the frontend get to know the increased version number after merging a tracing?
- is this route also called if there is no volume data? (i.e. skeleton only)
- does it handle empty data.zips gracefully?
- is dragging in a zipfile with multiple volume annotations also supported?
Yes, it updates the state internally after a successful response.
No, then only the skeleton updates are applied.
Yes.
No. |
Cool stuff!
Okay, let’s maybe create a follow-up issue for that then :) |
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.
Great job! I left some smaller feedback, but the main stuff looks really good 👍
frontend/javascripts/oxalis/model/reducers/volumetracing_reducer_helpers.js
Show resolved
Hide resolved
I hope I addressed all of the feedback. Feel free to test again 🙂 |
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.
Excellent :)
URL of deployed dev instance (used for testing):
Steps to test:
Issues:
[ ] Updated (unreleased) migration guide if applicable[ ] Updated documentation if applicable[ ] Adapted wk-connect if datastore API changes