@repobit/dex-system-design 0.23.11 → 0.23.13
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/CHANGELOG.md +15 -0
- package/package.json +5 -2
- package/schemas/README.md +33 -0
- package/schemas/component-manifest.json +695 -0
- package/schemas/page-schema.json +128 -0
- package/src/components/compare/compare.css.js +30 -88
- package/src/components/compare/compare.js +165 -149
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,21 @@
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
|
|
5
5
|
|
|
6
|
+
## [0.23.13](https://github.com/bitdefender/dex-core/compare/@repobit/dex-system-design@0.23.12...@repobit/dex-system-design@0.23.13) (2026-04-03)
|
|
7
|
+
|
|
8
|
+
### Bug Fixes
|
|
9
|
+
|
|
10
|
+
* **DEX-1014:** fix for barchart alignment
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
## [0.23.12](https://github.com/bitdefender/dex-core/compare/@repobit/dex-system-design@0.23.11...@repobit/dex-system-design@0.23.12) (2026-04-03)
|
|
14
|
+
|
|
15
|
+
**Note:** Version bump only for package @repobit/dex-system-design
|
|
16
|
+
|
|
17
|
+
|
|
18
|
+
|
|
19
|
+
|
|
20
|
+
|
|
6
21
|
## [0.23.11](https://github.com/bitdefender/dex-core/compare/@repobit/dex-system-design@0.23.10...@repobit/dex-system-design@0.23.11) (2026-04-01)
|
|
7
22
|
|
|
8
23
|
### Bug Fixes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@repobit/dex-system-design",
|
|
3
|
-
"version": "0.23.
|
|
3
|
+
"version": "0.23.13",
|
|
4
4
|
"description": "Design system based on Web Components.",
|
|
5
5
|
"author": "Iordache Matei Cezar <miordache@bitdefender.com>",
|
|
6
6
|
"homepage": "https://github.com/bitdefender/dex-core#readme",
|
|
@@ -11,11 +11,14 @@
|
|
|
11
11
|
},
|
|
12
12
|
"files": [
|
|
13
13
|
"src",
|
|
14
|
+
"schemas",
|
|
14
15
|
"README.md",
|
|
15
16
|
"CHANGELOG.md",
|
|
16
17
|
"LICENSE"
|
|
17
18
|
],
|
|
18
19
|
"exports": {
|
|
20
|
+
"./component-manifest": "./schemas/component-manifest.json",
|
|
21
|
+
"./page-schema": "./schemas/page-schema.json",
|
|
19
22
|
"./accordion-bg": "./src/components/accordion/accordion-bg.js",
|
|
20
23
|
"./accordion": "./src/components/accordion/accordion.js",
|
|
21
24
|
"./anchor": "./src/components/anchor/anchor-nav.js",
|
|
@@ -86,5 +89,5 @@
|
|
|
86
89
|
"volta": {
|
|
87
90
|
"node": "24.14.0"
|
|
88
91
|
},
|
|
89
|
-
"gitHead": "
|
|
92
|
+
"gitHead": "d009cffbbe3f294b3b3efea4834b9b25d4e7baa1"
|
|
90
93
|
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# Dex System Design Schemas
|
|
2
|
+
|
|
3
|
+
These files are the machine-readable contract for page generation:
|
|
4
|
+
|
|
5
|
+
- `component-manifest.json`
|
|
6
|
+
- Catalog of public tags, import entrypoints, and public props.
|
|
7
|
+
- `page-schema.json`
|
|
8
|
+
- Recursive JSON schema for a generated page tree.
|
|
9
|
+
|
|
10
|
+
Recommended n8n flow:
|
|
11
|
+
|
|
12
|
+
1. Load `component-manifest.json`.
|
|
13
|
+
2. Give the manifest plus a content brief to an LLM.
|
|
14
|
+
3. Ask the model to return JSON that validates against `page-schema.json`.
|
|
15
|
+
4. Validate the result.
|
|
16
|
+
5. Render the validated tree to HTML or a Lit template.
|
|
17
|
+
|
|
18
|
+
Suggested prompt shape:
|
|
19
|
+
|
|
20
|
+
```text
|
|
21
|
+
You are generating a page using only the components from component-manifest.json.
|
|
22
|
+
Return valid JSON matching page-schema.json.
|
|
23
|
+
Use only tags and props present in the manifest.
|
|
24
|
+
Only include imports that are required by the selected components.
|
|
25
|
+
Prefer simple, valid compositions over speculative props.
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
Important constraints:
|
|
29
|
+
|
|
30
|
+
- Treat `props` as component property names.
|
|
31
|
+
- If `attributeName` exists in the manifest, the renderer should emit that HTML attribute when serializing to markup.
|
|
32
|
+
- `children` may contain plain text or nested component nodes.
|
|
33
|
+
- The manifest is intentionally conservative. If a prop is not listed, the generator should not invent it.
|