@bicharts/chart-host 0.6.32 → 0.6.34
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 +6 -0
- package/dist/{chunk-P22NUGCZ.mjs → chunk-BQJHYOPP.mjs} +819 -808
- package/dist/index.mjs +3 -3
- package/dist/react.mjs +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -67,6 +67,12 @@ payload→source row mapping — which is the part you must not hand-roll:
|
|
|
67
67
|
> not an id in your table. Re-render a chart with filtered rows and its payload renumbers from
|
|
68
68
|
> zero, so the same integer now denotes a different record. Comparing indices across two charts
|
|
69
69
|
> does not throw — it quietly filters to the wrong thing.
|
|
70
|
+
>
|
|
71
|
+
> Rows built from `data.sample.json` already carry a `__rowIdx__` column (the sample's own
|
|
72
|
+
> positions). The payload builder owns that name: it drops an incoming `__rowIdx__` and writes
|
|
73
|
+
> each payload's positions itself, so the rows above need no cleaning. (Before 0.6.33 the
|
|
74
|
+
> incoming column was kept beside the new one and a filtered chart's clicks read it; on an older
|
|
75
|
+
> version, leave `__rowIdx__` out when you build `columns`.)
|
|
70
76
|
|
|
71
77
|
### The coordinated dashboard: one chart filters, the other highlights
|
|
72
78
|
|