Stream: IG creation
Topic: Case Sensitivity is a royal pain in the @#$
Eric Haas (Oct 09 2020 at 02:08):
I spent the last hour debugging which stems from case sensitive autobuild ( thank you LINUX :sarcasm:) and most of using case insensitive local machine ( thank you OS and Windows ! ). This is a pain to constantly debug only made worse by the fact that GitHub which does not change the case for a file name (which I keep forgetting) when you change it locally. So can we just make everything case insensitive in the publisher to stop wasting all this time?
for example I'm going to make a couple of template tweaks to make the file naming for type in pages -intro and -notes case insensitive so ValueSet.md and valueset.md and valueSet*.md are treated the same. Does anybody have any issues with that?
here is an example of what I mean:
here is a pagecontent directory:
├── OperationDefinition-example-notes.md
├── StructureDefinition-extension-blah-intro.md
├── StructureDefinition-extension-complex-intro.md
├──etc
which Would be equivalent to:
├── operationdefinition-example-notes.md
├── structureDefinition-extension-blah-intro.md
├── STRUCTUREDEFINITION-extension-complex-intro.md
├──etc
Right now the second won't be rendered...
Grahame Grieve (Oct 09 2020 at 04:17):
right now the IG publisher enforces case sensitivity where ever it can. Obviously you found somewhere that I missed. I do that because on OSs where there is case sensitivity, I can't always override that (and it's painful even where I can)
Last updated: Apr 12 2022 at 19:14 UTC
