-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Cell-level metadata] Update the Add metadata select #488
[Cell-level metadata] Update the Add metadata select #488
Conversation
Signed-off-by: stefanbabukov <[email protected]>
Signed-off-by: stefanbabukov <[email protected]>
Signed-off-by: stefanbabukov <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #488 +/- ##
==========================================
- Coverage 90.50% 89.86% -0.65%
==========================================
Files 160 166 +6
Lines 3498 3572 +74
Branches 390 395 +5
==========================================
+ Hits 3166 3210 +44
- Misses 311 340 +29
- Partials 21 22 +1
|
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.
There's some tests pending I think
Signed-off-by: stefanbabukov <[email protected]>
…l-level-meta Signed-off-by: stefanbabukov <[email protected]>
Signed-off-by: stefanbabukov <[email protected]>
@StefanBabukov wouldn't it be better to use the name |
Signed-off-by: stefanbabukov <[email protected]>
const snakeCasedKeysToPatch = _.mapKeys(body, (_value, key) => _.snakeCase(key)); | ||
const { cellMetadataFileId } = await new CellLevelToExperiment().find({ experiment_id: experimentId }).first(); | ||
await new CellLevel().updateById(cellMetadataFileId, snakeCasedKeysToPatch); |
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.
This call won't work, also we are allowing users to decide what to patch, and that's not something we want to do.
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.
This isn't part of the ticket anyways, so maybe you could just leave this function empty
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.
I'm using this to update the status of the upload. What's the problem here? Why would it not work?
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.
I mean rather than snake casing anything that arrives, just extract the upload status and update only that.
It's more or less what the patch of sample files const patchFile = async (req, res) => {
does
Signed-off-by: stefanbabukov <[email protected]>
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, I think there was one comment to address from iva too
Signed-off-by: stefanbabukov <[email protected]>
Description
Details
URL to issue
https://github.com/orgs/hms-dbmi-cellenics/projects/4/views/1?pane=issue&itemId=37286398
Link to staging deployment URL (or set N/A)
N/A
Links to any PRs or resources related to this PR
Integration test branch
master
Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.
Code updates
Have best practices and ongoing refactors being observed in this PR
Manual/unit testing
Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.
Documentation updates
Optional