Mapped keys do not preserve JSDoc documentation
#50 715 ouverte le 11 sept. 2022
Métriques du dépôt
- Stars
- (48 455 stars)
- Métriques de merge PR
- (Merge moyen 6j 17h) (9 PRs mergées en 30 j)
Description
Bug Report
🔎 Search Terms
mapping types with docs; preserve docs on mapped types
🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about this
⏯ Playground Link
Playground link with relevant code
💻 Code
All relevant code can be found in the example links.
Why doesn't TypeScript/Vscode preserve documentation / JSDoc for mapped types?
Using this example that appears in the TypeScript documentation itself, which you can quickly reproduce in Vscode locally, you can see the problem.
It is expected that when remapping the keys of a type object, the documentation would remain what was defined in the original/previous keys, but this does not happen. Nothing is preserved.
This sucks in the development context, because it requires us to have to repeat the documentation of a property or method, for example, in multiple places, thousands of times. This can lead to consistency issues as the code grows and loses the point of automating things.
Another directly related problem is in Index Signatures. Even if documentation is added, nothing is preserved. This also includes Union Types. An example can be seen here.
🙁 Actual behavior
JSDoc documentation is not preserved in mapped keys.
🙂 Expected behavior
Mapped keys must have JSDoc documentation of their original/previous names.