Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overwritten html files when two items of the same type but different case exist and the file system is case insensitive #2012

Closed
xaviergonz opened this issue Jul 22, 2022 · 1 comment
Labels
bug Functionality does not match expectation

Comments

@xaviergonz
Copy link

xaviergonz commented Jul 22, 2022

Search terms

ignore case, case, caseless, overwritten, html

Expected Behavior

Given:

  • Two exported items of the same kind (e.g. functions) that only vary in case (e.g. 'model' and 'Model')
  • It should generate a suffix if the generated html files would clash in a case insensitive file system (e.g. Windows or OsX) (e.g. functions/model.html, functions/Model-1.html)

Actual Behavior

  • The model.html file gets overwritten, so only one of those documents can be accessed in case insensitive file systems.

Environment

  • Typedoc version: 0.23.8
  • TypeScript version: 4.7.4
  • Node.js version: 16.16.0
  • OS: OSX 12.5
@xaviergonz xaviergonz added the bug Functionality does not match expectation label Jul 22, 2022
@xaviergonz xaviergonz changed the title Overwritten html files when two items of the same type but different case exists and the file system ignores case Overwritten html files when two items of the same type but different case exist and the file system ignores case Jul 22, 2022
@xaviergonz xaviergonz changed the title Overwritten html files when two items of the same type but different case exist and the file system ignores case Overwritten html files when two items of the same type but different case exist and the file system is case insensitive Jul 22, 2022
@xaviergonz
Copy link
Author

Excellent! Thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality does not match expectation
Projects
None yet
Development

No branches or pull requests

1 participant