Skip to content

Fix validation for primitives with no value and extensions#658

Open
andrzejskowronski wants to merge 3 commits intodevelopfrom
fix/test-empty-value-validation
Open

Fix validation for primitives with no value and extensions#658
andrzejskowronski wants to merge 3 commits intodevelopfrom
fix/test-empty-value-validation

Conversation

@andrzejskowronski
Copy link
Copy Markdown
Contributor

Description

This pull request updates the validation logic for FHIR primitives with extensions but no value, ensuring compliance with the FHIR specification.
Specifically, it changes the behavior so that such elements are now considered valid (instead of generating a warning), and updates both the PatternValidator and RegExValidator accordingly.

Validation logic updates:

  • Updated PatternValidator & RegExValidator to treat primitives with extensions but no value as valid per the FHIR spec, returning ResultReport.SUCCESS instead of a warning.

# Conflicts:
#	test/Firely.Fhir.Validation.Compilation.Tests.Shared/FhirTestCases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant