feat(vr): Save original non-standard VR

[alekschernof]

Hello, I encountered several issues with saving the dataset to a file.
After investigation I found that the source file has different vr that in dictionary And the main problem is that after the naturalizeDataset process we lose origin vr for these tags and in the denaturalizeDataset process we try to process tag with incorrect vr
and therefore we get the following errors when trying to write.

In dicom image (LUTData tag has incorrect vr. In standart it US)

We received that image and we get the following errors when trying to write

[netlify]

✅ Deploy Preview for dcmjs2 ready!

Name	Link
🔨 Latest commit	51ac8cd
🔍 Latest deploy log	https://app.netlify.com/sites/dcmjs2/deploys/6764253b9c4b4600086c41fb
😎 Deploy Preview	https://deploy-preview-414--dcmjs2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[pieper]

This sounds reasonable, but a couple things.

First, we need to have commits follow the commit message format. Here it would be something like feat(vr): Save original non-standard VR and also including a summary of the change in the rest of the commit message so that it's explained in git log without needing to refer back to the PR.

Also, please add a test for this. It can be simple, just make a dataset from scratch that has the incorrect VR and then run it through the round trip (go from namified javascript object to part 10, then back from part10 to namified object and back to part 10 and then back to namified and confirm that desired VR has been preserved).

[alekschernof]

This sounds reasonable, but a couple things.

First, we need to have commits follow the commit message format. Here it would be something like feat(vr): Save original non-standard VR and also including a summary of the change in the rest of the commit message so that it's explained in git log without needing to refer back to the PR.

Also, please add a test for this. It can be simple, just make a dataset from scratch that has the incorrect VR and then run it through the round trip (go from namified javascript object to part 10, then back from part10 to namified object and back to part 10 and then back to namified and confirm that desired VR has been preserved).

Hello, I renamed pr and commits by requirements and added simple test for naturalizeDataset and denaturalizeDataset with checks

[pieper]

Thanks LGTM 👍

[github-actions]

🎉 This PR is included in version 0.37.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀