Skip to content

Commit 09d60ab

Browse files
Document the changes for release, bump version
1 parent 4978303 commit 09d60ab

2 files changed

Lines changed: 6 additions & 19 deletions

File tree

release-notes.md

Lines changed: 5 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,11 @@
11
## Intro:
22

3-
This is a bugfix release with several stability and correctness improvements.
4-
5-
**Serialization**
6-
- Fixed an `OverflowException` when serializing large decimal values with old parsing stack
7-
- Switched `FhirClient` to use the modern POCO serializer for better consistency
8-
- Fixed size limitations when serializing base64-encoded data
9-
- Fixed the `pretty` option being ignored when calling `ToXml()`
10-
11-
**Snapshot generation**
12-
- Fixed incorrect behavior in collection merge when suppression extensions were involved, which could cause an index-out-of-range error or suppression being silently ignored
3+
This release includes a behavioral change in parsing alongside a minor bug fix. Please read the notes below carefully before upgrading.
134

145
**POCO / type system**
15-
- `ISourceNode` now has a direct `ToPoco()` extension method
16-
- Fixed `instant` values being stored incorrectly when converting from an untyped source
17-
- Untyped sources are now correctly associated with the model when building POCOs
18-
- Custom resources and datatypes are now easier to define and build as a `ClassMapping` for `ModelInspector`
19-
- Restored collection initializer syntax support on the `Parameters` class
20-
- Added `IVersionableConformanceResource` to R5 `NamingSystem`
6+
- The SDK now detects incorrectly cased element and resource type names. Two new error codes are introduced: `PVAL131` (`WRONG_CASED_ELEMENT`) and `PVAL132` (`WRONG_CASED_RESOURCE_TYPE`).
7+
8+
> **Breaking change:** Parsers running in strict mode will now report errors when receiving data with incorrectly cased element or resource type names. Data that was previously silently corrected during parsing will now cause parse errors instead. Make sure your data sources use the correct casing as defined by the FHIR specification. All non-strict modes (BackwardsCompatible, Recoverable, NoOverflow, and the default) continue to bind leniently, preserving the behaviour from previous SDK versions. The exact handling of wrong-cased names in lenient modes is subject to change in future major versions of the SDK.
219
2210
**Other fixes**
23-
- Resolver base class now allows returning `null`, leaving it to the caller to decide whether to throw
24-
- Dependencies downgraded to align with the target framework version
11+
- Fixed redundant null-checks and initialization logic in bundle link handling.

src/firely-net-sdk.props

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
<!-- Solution-wide properties for NuGet packaging -->
88
<PropertyGroup>
9-
<VersionPrefix>6.2.2</VersionPrefix>
9+
<VersionPrefix>6.3.0</VersionPrefix>
1010
<VersionSuffix></VersionSuffix>
1111
<Authors>Firely (info@fire.ly) and contributors</Authors>
1212
<Company>Firely (https://fire.ly)</Company>

0 commit comments

Comments
 (0)