@remit/ui 0.0.16 → 0.0.17

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remit/ui",
3
- "version": "0.0.16",
3
+ "version": "0.0.17",
4
4
  "type": "module",
5
5
  "files": [
6
6
  "src"
@@ -74,9 +74,15 @@ export const AllSelected: Story = {
74
74
 
75
75
  /**
76
76
  * The search has more matches than are loaded: an escalation notice offers a
77
- * real button (not prose) naming the total. Tapping it is what flips the
78
- * selection's identity from an id set to the search query (out of scope for
79
- * this kit the caller supplies the count once paging resolves it).
77
+ * real button (not prose) naming the scope. Tapping it is what flips the
78
+ * selection's identity from an id set to the search query (`useEscalatedDelete`
79
+ * in web-client). No count in the label yet the real client's own read path
80
+ * (`ThreadOperations.searchThreads`) only counts within a capped recency
81
+ * window short of paging the whole result set, and paging it just to seed a
82
+ * button label the user hasn't asked for yet would burn a request on every
83
+ * render of "all loaded selected" for a number that goes stale the moment new
84
+ * mail arrives. Tapping the button is what pays for the real count, via the
85
+ * counting state below.
80
86
  */
81
87
  export const EscalationAvailable: Story = {
82
88
  args: {
@@ -90,7 +96,7 @@ export const EscalationAvailable: Story = {
90
96
  tone: "info",
91
97
  text: "",
92
98
  action: {
93
- label: 'Select all 3,412 matching "npm"',
99
+ label: 'Select all matching "npm"',
94
100
  onClick: () => undefined,
95
101
  },
96
102
  },