Repository navigation
chore(deps): update dependency hl7.fhir.r4 to v6 - #127
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Contributor
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Max errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 2 | 0 | 0 | 0.12s | ||
| ✅ ACTION | zizmor | 2 | 0 | 0 | 1.7s | ||
| csharpier | 34 | 1 | 0 | 14.81s | |||
| ✅ EDITORCONFIG | editorconfig-checker | 68 | 0 | 0 | 0.25s | ||
| ✅ JSON | jsonlint | 18 | 0 | 0 | 0.13s | ||
| prettier | 18 | 1 | 0 | 1.03s | |||
| ✅ JSON | v8r | 18 | 0 | 0 | 5.02s | ||
| markdownlint | 2 | 2 | 0 | 0.78s | |||
| ✅ MARKDOWN | markdown-table-formatter | 2 | 0 | 0 | 0.43s | ||
| ✅ REPOSITORY | betterleaks | yes | no | no | 1.06s | ||
| ✅ REPOSITORY | checkov | yes | no | no | 20.86s | ||
| ✅ REPOSITORY | dustilock | yes | no | no | 0.03s | ||
| ✅ REPOSITORY | git_diff | yes | no | no | 0.01s | ||
| ✅ REPOSITORY | kingfisher | yes | no | no | 6.74s | ||
| ✅ REPOSITORY | osv-scanner | yes | no | no | 0.8s | ||
| ✅ REPOSITORY | secretlint | yes | no | no | 1.25s | ||
| ✅ REPOSITORY | syft | yes | no | no | 4.94s | ||
| ✅ REPOSITORY | trivy | yes | no | no | 13.64s | ||
| ✅ REPOSITORY | trivy-sbom | yes | no | no | 0.75s | ||
| ✅ REPOSITORY | trufflehog | yes | no | no | 5.2s | ||
| ✅ YAML | prettier | 5 | 0 | 0 | 0.43s | ||
| ✅ YAML | v8r | 5 | 0 | 0 | 7.36s | ||
| ✅ YAML | yamllint | 5 | 0 | 0 | 0.57s |
Detailed Issues
⚠️ CSHARP / csharpier - 1 error
Error ./Directory.Build.props - Was not formatted.
----------------------------- Expected: Around Line 46 -----------------------------
<ItemGroup>
<PackageReference Include="Microsoft.SourceLink.GitHub" PrivateAssets="all" />
</ItemGroup>
----------------------------- Actual: Around Line 46 -----------------------------
<ItemGroup>
<PackageReference
Include="Microsoft.SourceLink.GitHub"
Error ./src/FhirOperationDefinitionGen.Tests/FhirOperationDefinitionGen.Tests.csproj - Was not formatted.
----------------------------- Expected: Around Line 24 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" PrivateAssets="all" />
</ItemGroup>
----------------------------- Actual: Around Line 24 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference
Include="Microsoft.CodeAnalysis.Analyzers"
Error ./src/FhirOperationDefinitionGen/FhirOperationDefinitionGen.csproj - Was not formatted.
----------------------------- Expected: Around Line 12 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" PrivateAssets="all" />
<PackageReference Include="Hl7.Fhir.R4" PrivateAssets="all" GeneratePathProperty="true" />
----------------------------- Actual: Around Line 12 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference
Include="Microsoft.CodeAnalysis.Analyzers"
Error ./src/FhirParametersGenerator.Benchmark/FhirParametersGenerator.Benchmark.csproj - Was not formatted.
----------------------------- Expected: Around Line 12 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" PrivateAssets="all" />
</ItemGroup>
----------------------------- Actual: Around Line 12 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference
Include="Microsoft.CodeAnalysis.Analyzers"
Error ./src/FhirParametersGenerator.Tests/FhirParametersGenerator.Tests.csproj - Was not formatted.
----------------------------- Expected: Around Line 23 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" PrivateAssets="all" />
</ItemGroup>
----------------------------- Actual: Around Line 23 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference
Include="Microsoft.CodeAnalysis.Analyzers"
Error ./src/FhirParametersGenerator/FhirParametersGenerator.csproj - Was not formatted.
----------------------------- Expected: Around Line 11 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" PrivateAssets="all" />
</ItemGroup>
----------------------------- Actual: Around Line 11 -----------------------------
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" PrivateAssets="all" />
<PackageReference
Include="Microsoft.CodeAnalysis.Analyzers"
Checked 24 files in 14522ms.
⚠️ MARKDOWN / markdownlint - 2 errors
CHANGELOG.md:32 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Features"]
CHANGELOG.md:37 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Miscellaneous Chores"]
⚠️ JSON / prettier - 1 error
Checking formatting...
[warn] src/FhirOperationDefinitionGen.Tests/packages.lock.json
[warn] src/FhirOperationDefinitionGen/packages.lock.json
[warn] src/FhirParametersGenerator.Attributes/packages.lock.json
[warn] src/FhirParametersGenerator.Benchmark/packages.lock.json
[warn] src/FhirParametersGenerator.Demo/packages.lock.json
[warn] src/FhirParametersGenerator.Tests/packages.lock.json
[warn] src/FhirParametersGenerator/packages.lock.json
[warn] Code style issues found in 7 files. Run Prettier with --write to fix.
See detailed reports in MegaLinter artifacts
Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)
- Documentation: Custom Flavors
- Command:
npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,CSHARP_CSHARPIER,EDITORCONFIG_EDITORCONFIG_CHECKER,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_DUSTILOCK,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,REPOSITORY_KINGFISHER,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
from
June 23, 2026 07:26
31d8799 to
3a8fe4b
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
3 times, most recently
from
July 8, 2026 13:17
aad7476 to
7eae636
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
5 times, most recently
from
July 14, 2026 15:26
63e6712 to
9fb916c
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
5 times, most recently
from
July 23, 2026 23:52
0565b59 to
0136820
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
9 times, most recently
from
August 2, 2026 11:46
484aa9a to
0f810ac
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
from
August 5, 2026 17:44
0f810ac to
fa2268a
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
from
August 13, 2026 11:15
fa2268a to
3d78e44
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
3 times, most recently
from
August 26, 2026 20:43
abcf7d6 to
e1fded6
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
2 times, most recently
from
September 12, 2026 12:30
f02057e to
4cce38f
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
from
September 14, 2026 13:53
4cce38f to
714b063
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
from
October 1, 2026 16:13
714b063 to
28ffe2b
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
2 times, most recently
from
October 15, 2026 17:28
1a3e98b to
2f0d455
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
2 times, most recently
from
October 20, 2026 09:05
30438c7 to
81132ac
Compare
renovate
Bot
force-pushed
the
renovate/hl7.fhir.r4-6.x
branch
from
October 24, 2026 11:22
81132ac to
73b299e
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
5.13.4→6.8.0Release Notes
FirelyTeam/firely-net-sdk (Hl7.Fhir.R4)
v6.8.0: 6.8.0Intro:
This release adds a way to get the range of time a FHIR
dateordateTimecovers at itsprecision, and makes the FHIRPath conversion functions follow the FHIRPath specification for items
of a complex type: they no longer throw, but return empty or
false. There are no breaking APIchanges.
Date and time ranges
Interval<T>andDateTimeRangetypes inHl7.Fhir.ElementModel.Types.Interval<T>is ageneric interval whose sides are closed, open or unbounded, with
Contains,OverlapsandCovers.DateTimeRangeis a half-open range [Start,End) that also keeps thePrecision.DateandDateTimegetTryGetRange(out range),GetRange(TimeZoneInfo)andGetRange(TimeSpan). For example,2026-03covers all of March 2026, and10:00:00+01:00coversone second. A value without an offset is read in the given time zone, and the range is widened
where daylight saving skips or repeats a time.
PeriodgetsTryGetRange(out range)andTryGetRange(TimeZoneInfo, out range), from the startof
startto the end ofend. A missing side is unbounded.DateTimenow keeps the number of fraction digits fromParse(), so.000spans 1 ms. See issue#3628.
FHIRPath
The conversion functions
toBoolean(),toInteger(),toLong(),toDecimal(),toQuantity(),toString(),toDate(),toDateTime()andtoTime()now return empty for an item of a typethey cannot convert, such as a complex type or a resource, and the matching
convertsTo*()functions return
false, as the FHIRPath specificationrequires.
Patient.name.first().convertsToString()used to throw anInvalidOperationException("There is no known Cql/FhirPath type corresponding to the .NET type PocoNode") and now returns
false. The same goes for aCodingwithout acode, and aQuantitywithout a value or with acomparator. Items with a System type equivalent, like
Quantity, convert as before. See issue #3636.Changes:
This list of changes was auto generated.
v6.7.0: 6.7.0Intro:
This release adds an opt-in
PrimitiveValueConverterhook to the POCO deserializers, makes theJSON parser reject a primitive whose value is supplied twice, keeps repeated same-url extensions in
snapshots, makes the
SnapshotGeneratorreport differential paths with an empty segment, and fixesFHIRPath evaluation over invalid primitive values.
LocalTerminologyServicenow returns the full$validate-coderesult shape, and the terminology services accept repeatedtx-resourceparameters. There are no breaking API changes, but several changes alter behaviour or output that
callers may depend on: the new fatal parser issue
JSON135, the text ofOperationOutcome.IssueComponent.ToString(), warnings on inactive codes from$validate-code, and$expandrejecting repeated 0..1 parameters. See the behavioural notes below.Serialization
New
DeserializerSettings.PrimitiveValueConverterlets callers fix a wrongly typed primitive whileparsing, such as
"valueInteger": "42"or"active": "true", in both Json and Xml and in everymode,
Ostrichincluded. It is called only for values that are not of the type the primitivestores, plus
date,dateTime,instant,timeandinteger64, which can be the right type inthe wrong format. If it declines (returns the input) or throws a
FormatException,InvalidCastExceptionorOverflowException, the usual error is reported; any other exceptionpropagates. When not set, parsing is unaffected.
The string overloads of the Json deserializers now encode into a pooled buffer instead of
allocating a fresh
byte[]per parse, and the reader options the SDK uses are now public asSerializationUtil.FhirJsonReaderOptions. See issue #3598.An exception thrown while reading an Xml attribute is no longer hidden behind
"Can only exit from a resource part.".
The JSON parser now reports a fatal issue,
JSON135(PRIMITIVE_VALUE_SUPPLIED_TWICE), when aprimitive gets its value from both
nameand_name, e.g.{"name":"John","_name":"Johnny"}.The second value used to be dropped silently, with only the non-fatal
JSON134, so theNoOverflow,RecoverableandBackwardsCompatiblemodes accepted the data loss. This applies ineither property order and to elements of primitive arrays.
JSON134stays a non-fatal error fora primitive under
_namewhen no value was set yet. See issue #3533.FHIRPath
instant,integer64,integer,positiveIntorunsignedIntvalue no longermakes almost every FHIRPath expression that reaches it throw. Its value is now the unparsed
string, as it already was for
date,dateTimeandtime. Before, even$this is Referencethrew an
InvalidOperationExceptionfor such a node, so a sweep likedescendants().where($this is Reference)failed on the whole resource. TheValuegetter of thePOCO still throws.
Snapshot generation
SnapshotGeneratornow reports a specific issue (PROFILE_ELEMENTDEF_INVALID_PATH, code10021) for a differential element whose path has an empty segment, such as
Observation...unit,and skips that element. Such an element used to produce a phantom element
Observation.in thesnapshot, and any constraint on it, like a
fixedString, was silently lost. The rest of thedifferential is still processed. See issue #3591.
additional-bindingextensions on a binding, and the base already has one with that url, the snapshot now keeps all of
them. The first replaces the base extension, the rest are added next to it. They used to overwrite
each other, so only the last one survived. See issue #3625.
Terminology
LocalTerminologyService's ValueSet$validate-codenow returns the full result shape the HL7terminology ecosystem tests expect:
code,system,versionanddisplay, plus anissuesOperationOutcome with tx-issue-type codings and expressions relative to the input, for both valid
and invalid codes. A
CodeableConceptinput is echoed back, and inactive or non-active conceptsget
inactive/statusparameters.ValidateCodeResulthas new properties to read and writethese (
CodeableConcept,NormalizedCode,CausedByUnknownSystem,UnknownSystem,Inactive,Status), and newAdd*extension methods put an issue in itsissues. See issue #3631.The terminology services no longer reject an operation with repeated
tx-resourceparameters,which the tx-ecosystem IG requires servers to accept. Only repeats of the operation's 0..1
parameters are rejected; known 0..* and unknown parameters pass through. Each typed
*Parametersclass now lists its parameters in a public
KnownParameters.Other
PocoNode.Resolve("#id")no longer throws aNullReferenceExceptionwhen the resource has acontained resource without an
idbefore the one it refers to. A contained resource without aniddoes not match, and resolution continues. See issue #3613.OperationOutcome.IssueComponent.ToString()now writes a space before(further diagnostics:,as it already did before
(at. See issue #3621.Changes:
See More
Baseare emitted one level up (segment dropped from path and id)This list of changes was auto generated.
v6.6.0: 6.6.0Intro:
This release adds
net10.0to the frameworks the SDK targets, next tonet8.0andnetstandard2.1. It also letsFhirClientsend a resource directly as the body of an operationrequest, extends the FHIRPath
htmlChecks()function to string input, and makes theSnapshotGeneratorreport differential elements that are out of order. There is one binarybreaking change:
ElementNavFhirExtensions.HtmlChecks(PocoNode)now returnsbool?instead ofbool. Code that calls it needs to be recompiled. See the FHIRPath notes below.Platform support
net10.0, next tonet8.0andnetstandard2.1. This is additive: .NET 8and .NET 9 applications keep resolving to the
net8.0assets. On .NET 10, class mapping lookupsby name through
ModelInspector.FindClassMapping(ReadOnlySpan<char>)no longer allocate.net8.0remains supported until the next major version (SDK 7), even after Microsoft ends supportfor .NET 8 in November 2026.
netstandard2.1will be removed in a later minor release, once Unity 6.8 - whichreplaces Mono with CoreCLR and .NET 10 - has shipped. Its only remaining audience is Unity, and
Unity 6.8 can consume the
net10.0assets. If you depend on thenetstandard2.1assets foranother platform, please let us know.
FhirClient
instead of wrapping it in a
Parametersresource.WholeSystemOperationAsync,TypeOperationAsync,InstanceOperationAsyncandOperationAsynchave new overloads that take aResource, andTransactionBuilderhas matching overloads for its operation entries. Theexisting
Parametersoverloads are unchanged. See issue #3599.FHIRPath
htmlChecks()can now be invoked on astring. Its contents are validated as the content of anarrative
div, following the current FHIRPath build (FHIR-56303).Invoked on anything other than
xhtmlor astring, it now returns empty instead offalse. Tosupport this,
ElementNavFhirExtensions.HtmlChecks(PocoNode)returnsbool?instead ofbool,which is a binary breaking change for code that calls it directly. See issue #3604.
Snapshot generation
SnapshotGeneratornow reports a specific issue (PROFILE_ELEMENTDEF_INVALID_ELEMENT_ORDER,code 10020) when a differential element is out of order, i.e. when it constrains a base element
that precedes a base element already matched by an earlier differential element. The spec
requires
differential.elementandsnapshot.elementto follow the order of the basedefinition. Such elements could previously not be matched and were silently treated as new
elements, which surfaced downstream as a confusing error. The generator does not reorder the
differential. See issue #3600.
Dependencies
System.Reflection.Emit.LightweightandSystem.Bufferspackage dependencies were removed;both are part of every framework the SDK targets.
updated too, but are test-only and not part of the shipped packages.
Changes:
This list of changes was auto generated.
v6.5.0: 6.5.0Intro:
This release is mostly about the cost of parsing and serializing: allocations on the hot path of
(de)serialization are down substantially, and the serializers no longer emit empty objects or
elements. It also collects a series of
SnapshotGeneratorfixes and a concurrency fix interminology validation. There are no breaking API changes, but two
SnapshotGeneratorOperationOutcomeissue codes were renumbered to remove duplicates (10012 -> 10018,10014 -> 10019), which affects code that switches on those numbers. See the behavioural
notes below.
Serialization
{}) or empty elements (<x/>). A structure isopened only once it is known to have content, so an empty POCO - or one emptied out by a
SerializationFilter, as happens when summarizing - no longer produces output our owndeserializer rejects with
OBJECTS_CANNOT_BE_EMPTY/ELEMENT_CANNOT_BE_EMPTY. Summarizedresources now round-trip. See issue #3557.
NOOVERFLOWpreset, next toSTRICT.DeserializationMode.NoOverflowwas the one mode without a preset, reachable only by constructing the settings by hand. Thanks to
@sujeito-operator for the contribution. See issue #3532.
new FhirUri((Uri)null)no longer throws aNullReferenceException;FhirUrl(Uri)andCanonical(Uri)had the same problem. They now null-propagate, like the other primitivedatatype constructors. See issue #3578.
Performance
produced by model validation - which runs on every element in every deserialization mode except
SyntaxOnlyandOstrich- rather than the POCO graph it returns. Validation now allocates abouthalf of what it did, and the validation outcomes are unchanged. Measured on a Patient
StructureDefinition (88 KB): 5.1 MB allocated and 3.4 ms per parse, down to 2.5 MB and 1.8 ms.
With the validator off, the same parse went from 1.4 MB to 1.0 MB.
ClassMappinghot path no longer allocates per access. Two patterns - aLazyInitializerfactory allocated on every call, including the warm path, and a full locked snapshot of the
property mapping collection - sat on the per-element path of every (de)serialization and are now
gone.
on .NET 10 and later (
ClassMappingCollection.FindByName(ReadOnlySpan<char>)), with a fallbackon earlier frameworks.
Snapshot generation
NotSupportedException("Can only jump to local nameReferences") when a differentialelement carried a complex type profile reference of the form
canonicalUrl#elementNameandhad child constraints. See issue #3583.
Base- which is only a resolvableStructureDefinitionfrom R5 onwards - are now handled gracefully. Before R5,
Baseis treated as an empty root and awarning is emitted instead of the generator failing. Element matching and child handling for
anonymous and untyped logical model elements were improved along with it (VONK-10132).
OperationOutcomeissue codes were each used for two unrelated conditions. The duplicateshave been resolved:
PROFILE_ELEMENTDEF_SLICENAME_NOMATCHmoves from 10012 to 10018, andPROFILE_STRUCTURE_TYPE_MISSINGmoves from 10014 to 10019. Code that switches on thesenumeric codes needs updating. See issue #3587.
Terminology
LocalTerminologyService(multi-codingCodeableConceptvalidation) andValueSetExpander(grouping value sets) fanned out with
Task.WhenAll, so a single logical operation could callback into the caller-supplied
IAsyncResourceResolverfrom several threads at once. A resolverthat is not safe for concurrent use - a scoped EF Core-backed resolver, for instance - failed
with "A second operation was started on this context instance". Both sites now resolve
sequentially. See issue #3582.
Other
NewPocoBuildernow uses the FHIR definition, where available, todecide whether an element is primitive or complex, rather than relying on type-name heuristics.
This fixes misclassification of complex types in logical models identified by a canonical url.
MatchesPrefixno longer compares aReadOnlySpan<char>againstnull(CA2265). This is not abehaviour change - the comparison was correct - but it blocked building against
net10.0underTreatWarningsAsErrors. See issue #3580.Dependencies
were updated too, but are test-only and not part of the shipped packages.
Changes:
Bugfixes:
Others:
Task.WhenAllSee More
This list of changes was auto generated.
v6.4.0: 6.4.0Intro:
This release adds opt-in retention of XML comments in the POCO-based parser. There are no breaking changes.
Serialization
The POCO-based XML parser can now retain the comments found in the source document. Set
DeserializerSettings.RetainCommentstotrue(the default remainsfalse) and comments are attached to the parsed POCOs asSourceCommentsannotations, so that they survive a parse/serialize round-trip. See issue #3561.Dependencies
Changes:
This list of changes was auto generated.
v6.3.0: 6.3.0Intro:
This release includes a behavioral change in parsing alongside a minor bug fix. Please read the notes below carefully before upgrading.
POCO / type system
The SDK now detects incorrectly cased element and resource type names. Two new error codes are introduced:
PVAL131(WRONG_CASED_ELEMENT) andPVAL132(WRONG_CASED_RESOURCE_TYPE).Other fixes
Changes:
setLinkmethodThis list of changes was auto generated.
v6.2.1: 6.2.1Intro:
This is a bugfix release with several stability and correctness improvements.
Serialization
OverflowExceptionwhen serializing large decimal values with old parsing stackFhirClientto use the modern POCO serializer for better consistencySettings.SerializationEnginean instance ofFhirSerializationEngineFactory.Legacy.FromParserSettings(ModelInfo.ModelInspector, Settings.ParserSettings ?? new())as it was beforeprettyoption being ignored when callingToXml()Snapshot generation
POCO / type system
ISourceNodenow has a directToPoco()extension methodinstantvalues being stored incorrectly when converting from an untyped sourceClassMappingforModelInspectorParametersclassIVersionableConformanceResourceto R5NamingSystemOther fixes
null, leaving it to the caller to decide whether to throwChanges:
See More
This list of changes was auto generated.
New Contributors
v6.2.0: 6.2.0Intro:
RespectSuppressExtensionsetting toSnapshotGeneratorSettings(default:true) to allow consumers to opt out of suppress-extension handling during snapshot generation.Base.ClearOverflow()and corrected theNoOverflowdocstring.ITypedElementextension methods now useOverloadResolutionPriority(1), ensuring they are preferred overISourceNodeextensions for types implementing both interfaces (such asPocoNode).CachingTerminologyServicewhere resource or unrecognized parameter values could produce invalid cache keys.System.Text.JsonandMicrosoft.Extensions.Caching.Memoryto version10.0.7.Changes:
See More
This list of changes was auto generated.
v6.1.1: 6.1.1Intro:
Fixes wrong logic for BaseTerminologyService filtering parameters for duplicates on requests that accept 0..* on some parameters
Changes:
This list of changes was auto generated.
v6.1.0: 6.1.0Intro:
FHIRPathCompiledExpressionnow accepts0..*resources as input, removing the need for a dummy resource when the expression does not reference one.ModelInspectornow protects against cross-version contamination ofClassMappings, preventing type resolution errors when multiple library versions are used in the same process.MemberNameproperty for easier debugging.Changes:
See More
This list of changes was auto generated.
v6.0.2: 6.0.2Intro:
Mostly minor changes, but one breaking change where the PocoNode's ParentNode constructor has been removed, as it was not
necessary and is derived from the Parent.
Changes:
See More
This list of changes was auto generated.
v6.0.1: 6.0.1Intro:
Fixes Code having System and Value switched.
Leaves snapshot generation result usability to the caller rather than assuming error.
Changes:
This list of changes was auto generated.
v6.0.0Intro:
Firely .NET SDK v6.0.0
Changes:
Important
✂ PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.