Skip to content

docs: Update CHANGELOG with 19.9.1 fixes #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rkaraivanov wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: Update CHANGELOG with 19.9.1 fixes #224

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,17 @@
## 19.9.1 - 2026-10-27

### Fixed
- Render props ([#193](https://github.com/IgniteUI/igniteui-react/pull/193)):
- Templates read current React state instead of the first render's closure.
- Setting a render prop to `undefined` restores the element's default content. Grid components render nothing instead.
- Adding a render prop later no longer clears the others.
- Nested config objects, such as `IgrChat` `options`, keep their identity across renders and no longer re-render the element.
- Template updates no longer re-set every element property, e.g. `singleSelect` on each `IgrCombo` filter keystroke.
- React events raised in a template no longer fire the wrapper's handlers twice.
- Errors and suspensions stay in their slot, e.g. one grid cell, instead of reaching the app's error boundary.
- Async render props keep the previous content until the new one settles, and may return `PromiseLike<ReactNode>`.
- Templates invoked without a data context no longer throw.

## 19.10.0 - 2026-10-05 (only igniteui-react-grids)

### Changed
Expand Down
Loading