@vscode/codicons 0.0.46-4 → 0.0.46-6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.github/prompts/build-new-icons.prompt.md +32 -0
- package/dist/codicon.css +2 -1
- package/dist/codicon.csv +1 -0
- package/dist/codicon.html +22 -1
- package/dist/codicon.svg +1 -1
- package/dist/codicon.ttf +0 -0
- package/dist/codiconsLibrary.ts +1 -0
- package/dist/metadata.json +5 -0
- package/package.json +1 -1
- package/src/icons/account.svg +1 -1
- package/src/icons/share-window.svg +1 -0
- package/src/template/mapping.json +3 -0
- package/src/template/metadata.json +5 -0
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Build codicons and update mapping.json & metadata.json after adding new icons
|
|
3
|
+
argument-hint: List the new icon names you added (e.g. "wand, sparkle-filled")
|
|
4
|
+
tools: ['execute/runInTerminal', 'execute/getTerminalOutput', 'read', 'edit', 'search']
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
New SVG icons have been added to `src/icons/`. Your job is to build the font, update the template files, and verify everything is consistent.
|
|
8
|
+
|
|
9
|
+
## Steps
|
|
10
|
+
|
|
11
|
+
1. **Identify new icons** — compare `src/icons/*.svg` against the entries in `src/template/metadata.json` to find icons that don't have metadata yet. List them.
|
|
12
|
+
|
|
13
|
+
2. **Run the build** — execute `npm run build` in the `vscode-codicons` workspace root. Wait for it to finish and confirm it succeeds (exit code 0). If it fails, diagnose and fix the issue before continuing.
|
|
14
|
+
|
|
15
|
+
3. **Check mapping.json** — read `src/template/mapping.json`. The build's `fantasticon` step auto-generates this file. Verify each new icon appears as a primary name under its codepoint. If any new icon is missing, something went wrong in the build — investigate.
|
|
16
|
+
|
|
17
|
+
4. **Update metadata.json** — for each new icon that is missing from `src/template/metadata.json`, add an entry with this shape:
|
|
18
|
+
```json
|
|
19
|
+
"<icon-name>": {
|
|
20
|
+
"tags": ["<keyword1>", "<keyword2>", ...],
|
|
21
|
+
"category": "<category>",
|
|
22
|
+
"description": "<Short description of the icon>"
|
|
23
|
+
}
|
|
24
|
+
```
|
|
25
|
+
- **tags**: 4–8 search keywords describing the icon's visual appearance and usage.
|
|
26
|
+
- **category**: one of the existing categories already in the file (e.g. `"action"`, `"navigation"`, `"debug"`, `"file"`, `"user"`, `"git"`, `"layout"`, `"editor"`, `"symbol"`, `"status"`, `"media"`, `"device"`, `"misc"`). Pick the best fit.
|
|
27
|
+
- **description**: a concise one-line description.
|
|
28
|
+
- Keep entries sorted alphabetically by icon name.
|
|
29
|
+
|
|
30
|
+
5. **Run the metadata check** — execute `node scripts/check-metadata.js` and confirm zero missing or orphaned entries.
|
|
31
|
+
|
|
32
|
+
6. **Summary** — list the new icons added, their codepoints from mapping.json, and their metadata entries.
|
package/dist/codicon.css
CHANGED
|
@@ -6,7 +6,7 @@
|
|
|
6
6
|
@font-face {
|
|
7
7
|
font-family: "codicon";
|
|
8
8
|
font-display: block;
|
|
9
|
-
src: url("./codicon.ttf?
|
|
9
|
+
src: url("./codicon.ttf?8d7287840bcc6f7f1fe1a42270c665f4") format("truetype");
|
|
10
10
|
}
|
|
11
11
|
|
|
12
12
|
.codicon[class*='codicon-'] {
|
|
@@ -707,5 +707,6 @@
|
|
|
707
707
|
.codicon-terminal-secure:before { content: "\ec85" }
|
|
708
708
|
.codicon-chat-import:before { content: "\ec86" }
|
|
709
709
|
.codicon-chat-export:before { content: "\ec87" }
|
|
710
|
+
.codicon-share-window:before { content: "\ec88" }
|
|
710
711
|
.codicon-vm-pending:before { content: "\f101" }
|
|
711
712
|
.codicon-git-fetch:before { content: "\f102" }
|