fix: force load non-standard DICOM files#96
fix: force load non-standard DICOM files#96ziqiangxu wants to merge 1 commit intoImagingDataCommons:masterfrom
Conversation
pieper
left a comment
There was a problem hiding this comment.
Thanks for the contribution 👍
My main comment here is that this probably should be an optional parameter to the constructor with the default being False so we don't change the behavior of the API. Perhaps also there should be a setter so people can turn it on or off for a given client instance.
Also, just as a matter of convention we like to have more verbose commit messages that describe the motivation and design considerations for the suggested change. Doing this in an issue can help but for something simple like this providing more a more detailed commit message will let us discuss any issues here in the PR thread.
|
Agreed, I would certainly not want force loading of non-standard files to be default behaviour here. If we want to implement this, we should add a |
CPBridge
left a comment
There was a problem hiding this comment.
This would need to be an optional parameter, with default False, and be passed down from the various public methods that call _http_get_multipart_application_dicom
|




No description provided.