Closed ewoutkramer closed 7 years ago
I believe this is now ok as you've done the fhirpath location right?
Well, this is about the dotnet attributes, not the profile validator. The dotnet validation attributes have no knowledge of the (fhirpath/xpath) location, since all they know about is the POCO's, and poco instances (and elements in the instance) don't know anything about path.
Have no clue how to do this....
Do we even want need that stuff now? Should we ditch it? If we were to keep it, i can see how we'd implement the fhirpath given a property. (or at least have a fair idea, and could give it a whirl)
I don't know whether we need it now we have profile validation, maybe @cknaap can comment. The validation attributes itself are useful - if you have a control bound to them, they will show the error message (Forge uses this), just don't know whether we still need the path.
No one reacts, closing this issue.
This is more likely fhirpath locations now...