@gjsify/example-gtk-adwaita-storybook 0.36.0 → 0.38.0
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/README.md +4 -1
- package/dist/browser-main.js +589 -39
- package/dist/gjs.js +80 -4
- package/dist/gjs.node.mjs +75 -4
- package/package.json +6 -6
- package/src/browser/embed.ts +6 -15
- package/src/browser/main.ts +7 -10
- package/src/browser/overview/widgets.web.ts +118 -0
- package/src/browser/presentation/shortcut-label.web.ts +88 -0
- package/src/browser/stories.ts +4 -0
- package/src/metas.ts +2 -0
- package/src/overview/widgets.meta.ts +56 -0
- package/src/overview/widgets.story.ts +129 -0
- package/src/presentation/shortcut-label.meta.ts +90 -0
- package/src/presentation/shortcut-label.story.ts +92 -0
package/README.md
CHANGED
|
@@ -29,7 +29,10 @@ It is a showcase for three pieces of gjsify tooling working together:
|
|
|
29
29
|
Every target renders the SAME stories: the renderer-free `*.meta.ts` metadata is exported from
|
|
30
30
|
this package's `./metas` barrel and the shared logic lives in
|
|
31
31
|
[`@gjsify/storybook-core`](../../../packages/framework/storybook-core), so each renderer is a
|
|
32
|
-
thin adapter
|
|
32
|
+
thin adapter. That the sets really stay identical is machine-checked —
|
|
33
|
+
`scripts/check-storybook-story-parity.mjs` fails when a story is missing a rendering on any
|
|
34
|
+
target. There is no screenshot-comparison harness (#1052); behaviour parity across renderers is
|
|
35
|
+
held by the `@gjsify/adwaita-core/conformance` vectors.
|
|
33
36
|
|
|
34
37
|
## Prerequisites
|
|
35
38
|
|