@yuneta/gobj-ui 7.23.168 → 7.23.169

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.
Files changed (9) hide show
  1. package/README.md +2 -2
  2. package/dist/gobj-ui.cjs.js +390 -92
  3. package/dist/gobj-ui.es.js +390 -92
  4. package/package.json +1 -1
  5. package/src/broadcast_attrs.test.js +115 -0
  6. package/src/c_g6_nodes_tree.js +208 -19
  7. package/src/c_yui_treedb_topic_with_form.js +201 -68
  8. package/src/yui_row_search.js +56 -27
  9. package/src/yui_row_search.test.js +51 -1
package/README.md CHANGED
@@ -721,8 +721,8 @@ Counted off the record the table already has (`list_dict` fills the hook and
721
721
  fkey columns), so asking costs no round trip. The counting is
722
722
  `delete_impact.js`, pure and tested, because the shapes are the fiddly part: a
723
723
  hook or fkey value arrives as a list of refs, a dict keyed by id, or a single
724
- ref string — and a column can be BOTH hook and fkey, which counts on both
725
- sides, because the delete does both things.
724
+ ref string. A column that is BOTH hook and fkey still counts on both sides,
725
+ for stores written before the SDK began refusing that pair at schema parse.
726
726
 
727
727
  In the graph the node-delete popover carries the same two lines, and the
728
728
  **unlink** popover carries the reassurance that is its whole point: *neither