@lightdash/cli 2.304.0 → 2.305.1
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.
|
@@ -4,6 +4,16 @@ You are building a React data app that queries the Lightdash semantic layer. Thi
|
|
|
4
4
|
|
|
5
5
|
**Building a single reusable chart rather than an app?** Use the `reusable-visualization` skill before writing any code. A reusable visualization runs no query of its own — the host hands it rows, a field mapping, config option values and a colour palette — so the data and filter APIs below do not apply to it. That skill is the contract for those builds and overrides this guide wherever the two differ. Everything else here (environment, components, visual design) still applies. It says nothing about light/dark mode, and silence is not an override: **following the host's colour scheme is a platform contract that applies to a reusable visualization exactly as it does to an app** — see "Visual Design".
|
|
6
6
|
|
|
7
|
+
## User-facing responses
|
|
8
|
+
|
|
9
|
+
The person using the data app cares about what it shows and how it behaves, not how its code is implemented. For both the first build and follow-up changes, keep progress updates and final replies concise and non-technical unless otherwise asked:
|
|
10
|
+
|
|
11
|
+
- Describe the user-visible UI and behavior: what changed, where to find it, and what the user can do. Refer to controls and sections by their visible labels.
|
|
12
|
+
- Do not include source filenames or paths, line references, code snippets or tokens, component or function names, or other technical implementation details unless the user explicitly asks for them. Technical context in the prompt is not itself a request for a technical explanation.
|
|
13
|
+
- Explain limitations or unfinished work in terms of their effect on the app and any action the user can take, rather than exposing debugging or build details.
|
|
14
|
+
|
|
15
|
+
For example: "The date filter now updates all charts on this page. Use Clear filters to return to the full view."
|
|
16
|
+
|
|
7
17
|
## Iteration mindset
|
|
8
18
|
|
|
9
19
|
This pipeline is built for iteration — the user refines the app with follow-up prompts, and you have the full conversation history on every iteration. **Favor a responsive first build over upfront perfection.** Hit the core ask and ship; let the user tell you what to add.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lightdash/cli",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.305.1",
|
|
4
4
|
"description": "Lightdash CLI tool",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -22,8 +22,8 @@
|
|
|
22
22
|
"@actions/core": "1.11.1",
|
|
23
23
|
"@aws-sdk/credential-providers": "3.995.0",
|
|
24
24
|
"@casl/ability": "6.8.0",
|
|
25
|
-
"@lightdash/common": "2.
|
|
26
|
-
"@lightdash/warehouses": "2.
|
|
25
|
+
"@lightdash/common": "2.305.1",
|
|
26
|
+
"@lightdash/warehouses": "2.305.1",
|
|
27
27
|
"@sidvind/better-ajv-errors": "7.0.0",
|
|
28
28
|
"@types/columnify": "1.5.1",
|
|
29
29
|
"ajv": "8.18.0",
|