-
-
Notifications
You must be signed in to change notification settings - Fork 138
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Report a bug
Search Terms
Search Terms
ArkType VSCode Extension ArkDark syntax highlighting strings
Context
Context
- System:
- OS: Linux 6.18 CachyOS Linux
- CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
- Memory: 17.76 GB / 31.03 GB
- Container: Yes
- Shell: 4.3.3 - /bin/fish
- Binaries:
- code-oss: 1.107.1@994fd12 x64 - /usr/bin/code
- w/ tweak to access VSCode marketplace
- Node: 25.4.0 - /usr/bin/node
- npm: 11.7.0 - /home/noah/repos/HaloSPV3/HCE.Shared/node_modules/.bin/npm
- Deno: 2.6.5 - /usr/bin/deno
- code-oss: 1.107.1@994fd12 x64 - /usr/bin/code
- npmPackages:
- @ark/schema: 0.56.0
- @ark/util: 0.56.0
- arktype: ^2.1.20 => 2.1.29
- typescript: ^5.8.3 => 5.9.3
- arktype.arkdark: 6.6.0
Repro
//
// arktype syntax bug minimum reproduction
import { type } from 'arktype';
const nullableString = type('string | undefined');
/**
* {@link Thing}; A comment following a `type()` call behaves oddly. Especially with a string opener/closer e.g. `, ", or '.
*/
const Thing = nullableString;
const out = Thing.from('');
console.log(out);
//The string syntax highlighting bug affects VSCode's typescript language mode, but not when set to typescriptreact.
The following screenshots are arranged according to this table:
| ArkLight | typescript |
typescriptreact |
| ArkDark | typescript |
typescriptreact |
| Light Modern | typescript |
typescriptreact |
| Dark Modern | typescript |
typescriptreact |

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
Status
To do