fix(7338): Validation with unknown profile no longer cause error when setting FhirInstanceValidator.setErrorForUnknownProfiles(false)

[ttnTrifork]

This fixes #7338

• ValidatorWrapper now adheres to its property 'errorForUnknownProfiles' when validating a resource with an unknown profile

• Updated BaseHapiFhirResourceDao.validate to ensure $validate returns an error severity issue if target profile is unknown, regardless of the value of the ValidatorWrapper errorForUnknownProfiles property.

[robogary]

Formatting check succeeded!

[tadgh]

Heya, I appreciate the PR! I do have some concerns about it though. This specifically will change existing behaviour of the system in a non-backwards-compatible way. My understanding is that this PR makes $validate ignore the validator setting. I understand that this is what the spec says, but we prefer not to break existing behaviour unless absolutely necessary.

Is there a reason that you cannot just set this setting to true, and have the behaviour you intend?

Forgive me if I'm missing some nuance, validation is not my area of specialization.

[tadgh]

Heya, I appreciate the PR! I do have some concerns about it though. This specifically will change existing behaviour of the system in a non-backwards-compatible way. My understanding is that this PR makes $validate ignore the validator setting. I understand that this is what the spec says, but we prefer not to break existing behaviour unless absolutely necessary.

Is there a reason that you cannot just set this setting to true, and have the behaviour you intend?

Forgive me if I'm missing some nuance, validation is not my area of specialization.

Having now read the original issue (sorry I missed it originally), I see the reasoning much more clearly now. Approved pending the addition of a changelog in 8_8_0 changelogs folder.

[tadgh]

Approved pending a changelog

[ttnTrifork]

Thanks! I updated #7338 a bit so its easier to read