Closed driseley closed 5 years ago
@c-j-hughes Thanks for the review. I have added some unit tests for the EnvChangeTokenHandler class, and in the process of doing so realised that I had missed that the existing encoding lookup should be done with the resolved new charset, not the change value from the token, so have amended the code to address that.
If you are happy with this - would it possible to get a NuGet release of the driver with this fix and the PR for #108 (when it's ready), as we are currently dependent on a local build with these changes in them? Many thanks.
@c-j-hughes , @senseibaka - Many thanks for the release - that has helped us a lot (we were running a significant project risk with the local driver build)!
Proposed fix for #110