-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
refactor!(NODE-3427): remove md5 hashing from GridFS API #2899
Conversation
const specKeys = Object.keys(specDoc) | ||
.filter(key => key !== 'md5') | ||
.sort(); |
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 new spec tests that omit the md5 property for us, we should use those, but we are also behind on our GridFS sync so I defer that to later work.
@@ -9,7 +9,7 @@ import { MongoClient } from './mongo_client'; | |||
import { Db } from './db'; | |||
import { Collection } from './collection'; | |||
import { Logger } from './logger'; | |||
import { GridFSBucket } from './gridfs-stream'; | |||
import { GridFSBucket } from './gridfs'; |
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 can revert this, I figured now that its our only "gridfs" no need to name it after its implementation detail
_id: GridFSBucketWriteStream['id']; | ||
length: GridFSBucketWriteStream['length']; | ||
chunkSize: GridFSBucketWriteStream['chunkSizeBytes']; | ||
md5?: string; | ||
filename: GridFSBucketWriteStream['filename']; | ||
contentType?: GridFSBucketWriteStream['options']['contentType']; | ||
aliases?: GridFSBucketWriteStream['options']['aliases']; | ||
metadata?: GridFSBucketWriteStream['options']['metadata']; |
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.
We just don't do this anywhere else, so consistency
If you view the second commit forward you can get the reasonable looking diff, I first did some legacy clean up ensured the tests still worked without changes, then commiting that, made the drivers changes and fixed the test failures as a result.
NODE-3427