-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0884384
commit a137e94
Showing
2 changed files
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Title | ||
|
||
Date: 2024-05-30 | ||
|
||
Status: accepted | ||
|
||
## Context | ||
|
||
The best context for this can be gathered by reading | ||
[the TypeScript docs on `verbatimModuleSyntax`](https://www.typescriptlang.org/tsconfig/#verbatimModuleSyntax). | ||
|
||
The short version of this is that it helps TypeScript (and other compilers that | ||
strip types) to know whether to keep a module import or not. | ||
|
||
The idea is: If the import is only there to import types, then it's removed. If | ||
it imports values then it is not. | ||
|
||
## Decision | ||
|
||
Because it's more predictable behavior (and recommended by TypeScript) we will | ||
enable this rule. | ||
|
||
## Consequences | ||
|
||
The only change people should experience with this change is a more consistent | ||
and correct behavior. It's unlikely anyone will notice this change, but if they | ||
do it will probably be because it fixed a bug. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters