Microsoft/TypeScript
[ID] `--isolatedDeclarations` disallows `const` initialized with a regex literal
Aberta
#58.383 aberto em 1 de mai. de 2024
BugDomain: flag: isolatedDeclarationsHelp Wanted
Métricas do repositório
- Stars
- (108.860 estrelas)
- Métricas de merge de PR
- (Mesclagem média 6d 17h) (9 fundiu PRs em 30d)
Description
🔍 Search Terms
- isolatedDeclarations
- isolated declaration
✅ Viability Checklist
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals
⭐ Suggestion
I an unsure if it is a bug or a feature request...
An exported const without type annotation and initialized with a regex literal triggers the following error error TS9010: Variable must have an explicit type annotation with --isolatedDeclarations. in isolated declaration mode.
If I understand correctly, isolated declaration should allow unannotated const initialized with any literal?
📃 Motivating Example
See an example on the playground.
💻 Use Cases
This could avoid a trivial type annotation.