Stream: IG creation
Topic: Issue with history file and markown.
Eric Haas (Feb 20 2021 at 00:58):
FHIR30100 the markdown table is not rendered in the http://hl7.org/fhir/us/core/history.html description column correctly. Is GH markdown table not supported?
@Grahame Grieve ?
Grahame Grieve (Feb 24 2021 at 03:27):
not sure. feel free to play around with a local copy and see if it's a syntax problem or a limitation of the javascript library
Eric Haas (Feb 24 2021 at 16:32):
I don’t know how to generate the history file. That is only done at time of publishing.
Eric Haas (Feb 24 2021 at 16:32):
From the package list file
Eric Haas (Feb 24 2021 at 16:32):
Is there a way to render it locally?
Jose Costa Teixeira (Feb 24 2021 at 17:22):
I believe this is part of the publication process. AFAIK the publisher does the magic of keeping the history of the versions when it runs a build for publication
Eric Haas (Feb 24 2021 at 17:42):
it would be great if I could prevew is since it is actually doubling as a change log for my guide.
for example us core version history
Eric Haas (Feb 24 2021 at 17:55):
as an aside .... I'd like to see this as a best practice for IG authoring since it is useful for QAing the applied trackers and for review of the changes. I throw a copy of the package-list in the the _data directory (as YAML of course) and publish the section as a note to balloters so they can review too. It is created from a jira export and a bit of regex and then i manually enter the links for the changes and summary of changes the add a little markdown summary to give an overview. It makes applying changes more tedious and time consuming and thus costs more. Could add field for links to target changs and short summary of change to jira and then generate the change log for publishing @Lloyd McKenzie this is something we should consider adding to the list of IG editing topic?
Jose Costa Teixeira (Feb 24 2021 at 18:44):
The publication also works locally (that's the still to be documented bit)
Jose Costa Teixeira (Feb 24 2021 at 18:47):
I'll steal the idea of QAing the applied trackers. I've seen something related (and for us it should be easy because we use github ^ ^ )
Jose Costa Teixeira (Feb 24 2021 at 18:48):
I'm also trying to add a few SDLC aspects to the IG publication, so +1 to move forward
Eric Haas (Feb 24 2021 at 19:03):
Jose Costa Teixeira said:
The publication also works locally (that's the still to be documented bit)
how can I do this?
Jose Costa Teixeira (Feb 24 2021 at 19:07):
that's the still to be documented bit :)
Jose Costa Teixeira (Feb 24 2021 at 19:10):
the question is when - and the answer is when someone wants to have fun trying it and documenting for others (I tried, failed), or when Grahame reaches that point in his backlog. I asked him a few days ago, so now we wait :)
Grahame Grieve (Feb 24 2021 at 20:12):
I don’t know how to generate the history file.
Go to the page. and save it locally,. and then hack around with the local copy
Lloyd McKenzie (Feb 24 2021 at 23:47):
Eric Haas said:
is something we should consider adding to the list of IG editing topic?
Sure.
Last updated: Apr 12 2022 at 19:14 UTC
