Stream: IG creation
Topic: searchform issue -- how to resolve?
Saul Kravitz (Oct 07 2020 at 13:56):
Is there anything I can do to resolve this error?
Lloyd McKenzie (Oct 07 2020 at 14:32):
Are you using one of the standard HL7 templates?
Eric Haas (Oct 07 2020 at 14:46):
that happens to me when page is is being slurped up and rendered by the publisher, but is not in a nominated pages directory and it may have front matter?? I forget the details now but look at your tree sctructure and do you want it to be published?
Lloyd McKenzie (Oct 07 2020 at 15:02):
Stand-alone pages aren't slurped up...
Saul Kravitz (Oct 07 2020 at 18:52):
Yes. hl7.fhir.template#current
Grahame Grieve (Oct 07 2020 at 19:08):
it will be fixed in the next release
Jean Duteau (Oct 14 2020 at 16:29):
I still have some of Saul's error. Not the first part but the 2nd error - The link 'history.html' for "History" cannot be resolved - on searchform.html.
Grahame Grieve (Oct 14 2020 at 19:14):
that's my problem
Etienne Cantineau (Nov 05 2020 at 08:21):
Any news about this error?
Grahame Grieve (Nov 05 2020 at 11:28):
you should not be getting it anymore
Etienne Cantineau (Nov 05 2020 at 12:35):
@Grahame Grieve I'm still getting it
http://build.fhir.org/ig/ec-ehealth/Build-source/branches/master/qa.html
https://github.com/ec-ehealth/Build-source
with 3 new errors since 1.1.39 "The link 'valueset-diagnostic-requests.html' for "here" cannot be resolved"
Grahame Grieve (Nov 05 2020 at 21:15):
These 3 new errors are an unfortunate thing. I added rendering of ElementDefinition.binding.description for an HL7 project. That's find, but it turns out that this was never rendered in the base specification, and errors in that element in base specification are not picked up. The binding description in question here is:
"description" : "Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html).",
Grahame Grieve (Nov 05 2020 at 21:16):
two errors there in the markdown but the serious one is the reference for [here] is not valid.
I guess our options are:
- make rendering the binding description an option (doesn't help if you want to
- fix this particular binding by hack in the IG publisher
Grahame Grieve (Nov 05 2020 at 21:22):
others?
Lloyd McKenzie (Nov 05 2020 at 23:02):
I prefer the hack, presumably it'll go away once we put out 4B?
Grahame Grieve (Nov 05 2020 at 23:42):
I wouldn't count on that at all. R4B is not a technical correction for R4, and the tooling won't be able to treat it as such. The tooling will have to call it something else. APIs may be able to adopt it as a painless in place upgrade but they'll have to change their stated version
Jean Duteau (Nov 13 2020 at 17:26):
Etienne Cantineau said:
"The link 'valueset-diagnostic-requests.html' for "here" cannot be resolved"
I have four of these errors in my guide. I'm assuming that there is nothing to do but put this in ignoreWarnings.txt?
Lloyd McKenzie (Nov 13 2020 at 18:02):
It's a known issue. Publisher is now exposing stuff from core that wasn't before - and the links in core are broken
Lloyd McKenzie (Nov 13 2020 at 18:02):
Grahame's got it on his list. (It's a LONG list...)
Marcel Hanselmann (Oct 06 2021 at 16:28):
is there any hope that this problem will be solved in the foreseeable future? That would be great, I hope Gahame's list is not LIFO
Grahame Grieve (Oct 06 2021 at 21:38):
@Marcel Hanselmann there's a bunch of errors in this spec. When you say 'this problem', which one do you mean?
Marcel Hanselmann (Oct 21 2021 at 08:14):
no, forget it, in the mean the error is solved. sorry and thank you for the fix.
Last updated: Apr 12 2022 at 19:14 UTC
