chore(release): 2.0.0

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -8,12 +8,10 @@ body:
           value: |
               Thanks for the suggestion. Please search existing issues first.
 
-              Row grouping, a tree data model, master and detail rows, range selection,
-              aggregation and xlsx export are deliberately not in this package; they are
-              planned for a separate pro package. The kernel already renders nested rows as a
-              `treegrid`, and infinite scroll is a shape this package supports today —
-              `rowModel: 'server'` with `virtualization()`, appending as the window nears the
-              end of what is loaded. See `/server/infinite` in the playground.
+              Row grouping, tree data, master and detail rows, range selection,
+              aggregation and xlsx export all ship here. Register the feature module
+              you need and check the playground route for it before opening an issue:
+              a request that is already answered costs you a wait and us a reply.
 
     - type: textarea
       id: problem

MIGRATING.md

@@ -0,0 +1,95 @@
+# Upgrading to 2.0
+
+Almost everything in this release is additive: register a feature you did not
+have before and it works. Four things are not, and this is all of them.
+
+## `DataGridLabels` gained 147 members
+
+The new features brought their own wording, and the label table is one table.
+If you hand the grid a subset, which is the usual way, nothing changes:
+
+```ts
+createDataGrid({ labels: { search: 'Find...' }, columns, data, getRowId })
+```
+
+If you built a complete `DataGridLabels` of your own and passed it as the base
+of `mergeLabels`, it no longer type-checks, because it is now missing 147
+members. Merge onto the built-in table instead:
+
+```diff
+-mergeLabels(overrides, myCompleteTable)
++mergeLabels({ ...myCompleteTable, ...overrides })
+```
+
+## A blank cell now passes `neq` on a number
+
+A text column has always kept a blank on `notEqual`: a cell with no word in it
+is not the word being excluded. A number column dropped it, from one guard
+applied to every numeric comparator at once. They agree now, and the text
+reading is the one that won.
+
+If you were relying on `neq` to exclude blanks, say so:
+
+```diff
+ setColumnFilter('score', {
+-    kind: 'number', op: 'neq', value: 5
++    kind: 'group',
++    join: 'and',
++    conditions: [
++        { kind: 'number', op: 'neq', value: 5 },
++        { kind: 'number', op: 'notBlank' }
++    ]
+ })
+```
+
+The server contract's reference implementation in
+`src/tests/server-contract-ops.test.ts` shows the same rule, so a server you
+wrote against it needs the same change.
+
+## A typed column draws text it cannot parse
+
+A `type: 'number'` column handed `notanumber`, or a `type: 'date'` column
+handed `1234-56-78`, used to draw an empty cell. The value was in the row and
+the editor opened on it; only the screen said nothing was there. It now falls
+back to the raw text, so what the data holds is what you see.
+
+A blank cell is unaffected: `null`, `undefined` and `''` still draw the
+column's `emptyText`.
+
+This reaches masking too. A `policy()` rule that substitutes a string into a
+typed column used to blank the cell; the mark is drawn now, which is what the
+same rule already did on an untyped column.
+
+If you assert on a cell that cannot be parsed, it changed:
+
+```diff
+-expect(cell.textContent).toBe('')
++expect(cell.textContent).toBe('notanumber')
+```
+
+## The loading skeleton draws cells
+
+A row of skeletons used to be a `role="row"` around plain divs, which a screen
+reader cannot read and axe reports. Its cells now carry `role="gridcell"`.
+
+A test asserting that no `gridcell` exists while loading will fail. Assert on
+what it meant instead - that no data is on screen:
+
+```diff
+-expect(container.querySelectorAll('[role="gridcell"]')).toHaveLength(0)
++const cells = [...container.querySelectorAll('[role="gridcell"]')]
++expect(cells.every((cell) => cell.textContent?.trim() === '')).toBe(true)
+```
+
+## Worth knowing, but not breaking
+
+`DateFilterOp` gained `notEqual`. A `switch` of your own over that union is no
+longer exhaustive, which TypeScript will point out if you asked it to.
+
+The footer's page range separates the two numbers with a hyphen; it used to use
+an en dash. If you snapshot that string, it changed.
+
+A grid's language is set per grid, through `locales` and `locale` on
+`createDataGrid`. That has not changed, but it is worth repeating now that
+there is far more wording to translate: two grids on one page may speak
+different languages, and nothing global has to be put back afterwards.