fix: corrupted docx issue caused by duplicate extensions in ContentType.xml with different casing #400
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.
Description
This PR addresses a bug where the ContentType.xml file could be corrupted due to duplicate entries of the same file extension with different casing. For example, if a template specifies an uppercase extension (JPG), but the generated report inserts a lowercase extension (jpg), the ContentType.xml ends up with two entries:
As a result, the DOCX file becomes invalid.

Solution
To fix this issue, we updated the ensureContentType function to be case-insensitive when adding new extensions. This change ensures that only one entry is created for a given extension, regardless of its casing.
Changes
• Updated ensureContentType to treat extensions in a case-insensitive manner.
How to reproduce: