Fix file naming conflict error in schemas-md on macOS APFS (case-insensitive) #122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our schemas, there are terms with similar names that only differ in their casing, which leads to the generation of markdown files like:
AgeRange.md
ageRange.md
Value.md
value.md
This presents issues on case-insensitive filesystems (such as macOS APFS in its case-insensitive configuration).
To resolve this issue, I modified the parsing script. Now, the files are named distinctly to avoid conflicts:
AgeRange.md
has been renamed toAgeRange_PXF.md
Value.md
has been renamed toValue_PXF.md
Additionally, all links to these files have been updated accordingly.