FHIR Chat · Markdown Descriptions · conformance

Stream: conformance

Topic: Markdown Descriptions


view this post on Zulip Brian Postlethwaite (Jul 09 2016 at 05:49):

Seems that the descirption properties in the conformance resources was changed from string to Markdown.
This will likely effect Forge and other editors.
From the dotnet client perspective, looking for opinions in if we should add a native string representation in the c# object model.

view this post on Zulip Grahame Grieve (Jul 09 2016 at 07:54):

I just changed it. Don't you use a native string representation for markdown? You should

view this post on Zulip Grahame Grieve (Jul 09 2016 at 08:00):

that's the point - it's just string.

view this post on Zulip Brian Postlethwaite (Jul 09 2016 at 11:04):

Thanks to the extensions all the primitives have a wrapper to hold them, and the value within.
For convenience we also code generate a native property (in this case the string)
Was considering adding a helper to validate the markdown

view this post on Zulip Grahame Grieve (Jul 09 2016 at 11:36):

well, markdown is the same a string - should have the same signature.

view this post on Zulip Grahame Grieve (Jul 09 2016 at 11:36):

it might be possible to emebd markdown rendering inside the object model, but I suspect not - it's too contextual. And you can't validate markdown :-(

view this post on Zulip Brian Postlethwaite (Jul 09 2016 at 11:50):

Thanks. Wasn't going to try and do anything ourselves. Will update the generator to output the string convenience property also.


Last updated: Apr 12 2022 at 19:14 UTC