3.0.0-preview.3 Release

This is a pre-release package, we would appreciate it if people could test this package and raise any issues, so we can iron out any kinks before we go gold with 3.0.0.0.

We are hoping this is the final preview version ahead of 3.0.0.0.

On top of the previous preview release this release includes the following changes:

Bug Fixes

• #185 Escape.cs Improvements - hapi implementation port. By @milkshakeuk (fixes for #103)
• #192, #202 Update HL7 v. 2.3 IN1 and IN2 repeat flags for some fields. By @afaonline (fixes #191)
• #200 PipeParser Enhancements - Fix issues related to unexpected segments. By @milkshakeuk (fixes #51, #55, #56, #72, #101)
• #197 Fixes Exceptions and permanent Hang when parsing bad input, Adds bad input tests. By @JlKmn (fixes #196, #198)
• #205 Added additional bad inputs and enhanced error handling. By @AMCN41R (fixes #203)
• #217 Add changes to fix bad input from fuzzing. By @milkshakeuk (fixes #210)

Other

• #135, #137 Fix XML Build warnings. By @AMCN41R (fixes #128)
• #140 Add license for nHapi. By @milkshakeuk (fixes #119)
• #143 Add StyleCopAnalyzers to main projects. By @AMCN41R (fixes #138)
• #141 Create basic GitHub Actions for pull requests. By @milkshakeuk (partially addresses #124)
• #142 Add code coverage to the CI/CD, plus build status workflow for master. By @milkshakeuk (partially addresses #124)
• #145 Code Climate Coverage. By @milkshakeuk (partially addresses #124)
• #147, #148 Enable dependabot support to the repository. By @milkshakeuk
• #201 Normalize all the line endings. By @milkshakeuk
• #204 Create Default GitHub Code Scanning Workflow. By @milkshakeuk

Breaking Changes
Default escape sequence for carriage return has changed from \X000d\ to \X0D\ which brings it inline with other libraries and InterSystems ensemble.

However if you rely on the old escape sequence of \X000d\ for carriage returns you can now configure this, see #185 for options.

The latest PipeParser implementation from hapi has been ported over to nHapi, there aren't any breaking changes that I am aware of, only benefits, however if you relied on the specific behaviour of the old PipeParser.cs then you can use LegacyPipeParser.cs instead, which is the old implementation.