@ai-matrx/records-ui 0.58.0 → 0.60.0

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.59.0
+
+**Three things the browser walks found by using the builders on real businesses.**
+
+* **A booking page's day rows lied about what it would offer.** Every day started
+  unticked and read "not taking bookings", while `custom._booking_availability`
+  substitutes Monday-to-Friday nine-to-five for an empty window list — so a
+  person who saved without touching the days was told the page offered nothing
+  and got a page offering the whole working week. `BookingBuilder` now opens on
+  the working week, and once the store has answered, the rows are ITS answer.
+* **Both builders offered questions a stranger could never answer.** Ironclad
+  Mobile Mechanic ticked "Customer" on his booking page — a relation Field — a
+  visitor typed her name, and the store refused at the last step with *"Customer
+  points at something that is not there"*, after her slot was already held. A
+  relation holds the identity of a record in a Table she cannot open. The new
+  `publiclyAnswerable` / `askableFields` / `whyNotAskable` decide what a public
+  page may ask for (out: relation, member, attachment, formula, lookup, rollup)
+  and both `FormBuilder` and `BookingBuilder` use them — the Fields left out are
+  NAMED with the reason, in the place somebody would have ticked them.
+* The Booking and Portal builders and the Digest scheduler carry the container
+  queries 0.57.0 gave the form builder, so all four are one column in a rail.
+
+**Consumer action:** none.
+
 ## 0.58.0
 
 **A word pasted into a choice column becomes that option — and a paste is no