| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat: add context for array operation Currently it is very hard to figure out in the middleware what array operation happend to lead to the current array state. There are cases were this information is valuable. To support this all update actions can now have a 'context'. Here we added a specific 'UpdateArrayContext'. Contributed on behalf of STMicroelectronics | 2 年前 | |
core: handle nullable object/array in generateUISchema Treat ['null', T] type arrays as nullable T for UI generation so that nested nullable objects traverse their properties instead of producing a bare Control. This avoids infinite recursion in object renderers that regenerate the UI schema for nested nullable objects. Fixes #2411 | 4 个月前 | |
Apply ESLint auto fixes Part of #1551 | 3 年前 | |
deps(dev): Update various dev dependencies (#2503) * dev: Update pinned pnpm version to 10.22.0 * deps(dev): Upgrade to lerna 9 * deps(dev): Upgrade cross-env to ^10.1 and rimraf to ^6.1 * deps(dev): Upgrade to jest and ts-jest v29 - Upgrade jest to ^29.7.0 - Add now needed explicit jest-environment-jsdom where needed - vue: Add now needed module name mapper for @vue/test-utils - Upgrade ts-jest to ^29.4.5 - vue-vanilla: Replace outdated vue-jest with @vue/vue3-jest * deps(dev): Upgrade to latest jsdom ^27.2.0 With this, remove obsolete jsdom-global dependency * deps(dev): Upgrade to vite ^5.4.21 * deps(dev): Align @types/jest with jest 29 and remove it from repo root - Remove @types/jest from root package.json and add to consuming packages - Align @types/jest with jest 29 - Fix affected cell.test.ts | 10 个月前 | |
fix(core): refactor update data to avoid lodash issues (#2585) Fixes #2102 Fixes #2397 Replace the lodash/fp/set call in UPDATE_DATA with a dedicated helper. This fixes issues with numeric segments (e.g. "group-key.15") and bracket characters in property names (e.g. "test[0]"). Improvements on top of the lodash/fp/set replacement: - Store "__proto__" segments as own properties via defineProperty and traverse own properties only, so such keys neither corrupt the container's prototype nor get dropped. Clone containers key-by-key because downleveled object spreads assign instead of define. - Read the updater's old data with resolveData instead of lodash get, so reads use the same literal path semantics as writes. - Fall back to lodash's index heuristic when creating missing containers without schema type information. - Match lodash's isIndex semantics with a strict index regex instead of Number() coercion. - Avoid strict-mode TypeErrors when unsetting non-index array properties (e.g. "length") and return the same reference when there is nothing to unset. - Treat an empty path as addressing the root, and replace non-object root data instead of spreading it. Also documents the path semantics change in MIGRATION.md and adds unit tests for setDataAt/unsetDataAt. Co-authored-by: Darius Lesch <darius.lesch@proton.me> | 2 个月前 | |
fix(core): refactor update data to avoid lodash issues (#2585) Fixes #2102 Fixes #2397 Replace the lodash/fp/set call in UPDATE_DATA with a dedicated helper. This fixes issues with numeric segments (e.g. "group-key.15") and bracket characters in property names (e.g. "test[0]"). Improvements on top of the lodash/fp/set replacement: - Store "__proto__" segments as own properties via defineProperty and traverse own properties only, so such keys neither corrupt the container's prototype nor get dropped. Clone containers key-by-key because downleveled object spreads assign instead of define. - Read the updater's old data with resolveData instead of lodash get, so reads use the same literal path semantics as writes. - Fall back to lodash's index heuristic when creating missing containers without schema type information. - Match lodash's isIndex semantics with a strict index regex instead of Number() coercion. - Avoid strict-mode TypeErrors when unsetting non-index array properties (e.g. "length") and return the same reference when there is nothing to unset. - Treat an empty path as addressing the root, and replace non-object root data instead of spreading it. Also documents the path semantics change in MIGRATION.md and adds unit tests for setDataAt/unsetDataAt. Co-authored-by: Darius Lesch <darius.lesch@proton.me> | 2 个月前 | |
deps: Upgrade karma & ava to get rid of critical vulnerabilities Upgrade various dependencies to get rid of critical vulnerabilities in dependencies as reported by `pnpm audit`: - Remove obsolete ava and source-map-support root dev dependencies - Upgrade ava dependencies to ^6.1.2 and adapt tests and config accordingly - Completely remove obsolete source-map-support dep from vanilla-renderers - Upgrade karma dependencies to ^6.4.1 and karma-webpack to ^5.0.0 | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 4 个月前 | ||
| 3 年前 | ||
| 10 个月前 | ||
| 2 个月前 | ||
| 2 个月前 | ||
| 2 年前 |