FHIR Chat · temp files readme.md

Stream: IG creation

Topic: temp files readme.md

Eric Haas (Oct 19 2020 at 19:39):

I added README.md to all my input folders to help with maintenance

ERICS-AIR-2:input ehaas$ tree -L 2 -P "_*.*"
.
├── Archives
│   ├── MedStatement_graveyard
│   ├── _README.md
│   └── includes_archive
├── Drafts
│   ├── _README.md
│   ├── draft-examples
│   ├── draft-pages
│   └── draft-resources
├── data
│   └── _README.md
├── examples
│   └── _README.md
├── fsh
│   └── _README.md
├── history
│   └── _README.md
├── images
│   ├── _README.md
│   └── source
├── includes
│   └── _README.md
├── pagecontent
│   └── _README.md
├── resources
│   └── _README.md
├── resources_spreadsheets
│   └── _README.md
└── resources_yaml
    └── _README.md

and now getting annoying build errors ...

Exception in thread "main" java.lang.Error: Error generating build: the file /Users/ehaas/Documents/FHIR/US-Core-R4/temp/pages/_includes/_README.md is being generated more than once (may differ by case)
    at org.hl7.fhir.igtools.publisher.Publisher.checkMakeFile(Publisher.java:2821)
    at org.hl7.fhir.igtools.publisher.Publisher.generateHtmlOutputs(Publisher.java:6272)
    at org.hl7.fhir.igtools.publisher.Publisher.generate(Publisher.java:4658)
    at org.hl7.fhir.igtools.publisher.Publisher.createIg(Publisher.java:858)
    at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:707)
    at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:7756)

is there a way to ignore a particular file of directory ( in Jekyll they recommend prepending a _, ., #, or ~) ?

Eric Haas (Oct 19 2020 at 20:32):

@Chris Moesel this might be a sushi thing. Is there a way to to have it not generate a page in the implementation resource for a particular file in input/pagecontent?

Chris Moesel (Oct 19 2020 at 21:34):

Yes and no. If you define pages in your sushi-config.yaml then SUSHI should just transfer your definition to definition.page in the IG and not generate any of its own. But if you don't define pages, then SUSHI will generate the definition.page content based on all the .xml and .md files it finds in the pages or pagecontent folder.

Honestly, we didn't anticipate anyone having.md files in pagecontent that they didn't want to be a page. Do you feel like this is a common enough use case to warrant special behavior in SUSHI?

Chris Moesel (Oct 19 2020 at 21:35):

Or is it enough that you have the pages escape hatch in sushi-config.yaml?

Eric Haas (Oct 19 2020 at 23:36):

Sushi does a great job of making the Implementation Guide Resource based on the content so I don't have to. I will do a bash script workaround this for now. This is a balancing act between github features and the publisher.

Last updated: Apr 12 2022 at 19:14 UTC

Main menu