@refinedev/core@5.0.12

Patch Changes

• #7372 59c6470ca0ecff0588f749ef4530312e7537bfdd Thanks @alicanerdurmaz! - fix(core): preserve custom getList response fields in useList and useTable results.

  We had an edge case where custom fields returned from getList were available on query.data but dropped from result. Now those extra fields are preserved in both useList and useTable.

@refinedev/mui@8.0.2

Patch Changes

• #7345 af721fe26017cbe11ec997574908b40862a51a63 Thanks @tysoncung! - fix(mui): respect custom startIcon when hideText is true on all button components

  When hideText={true} is used with a custom startIcon, all MUI button components (ShowButton, EditButton, DeleteButton, CloneButton, CreateButton, ListButton, RefreshButton, SaveButton, ExportButton, ImportButton) ignored the custom icon and always showed the default one. This also caused two icons to appear at the same time.

  Now the custom startIcon is used when provided, and the default icon is only used as a fallback.

  Resolves #7343

@refinedev/devtools@2.0.5

Patch Changes

• Updated dependencies [b319c8a7a2f11896008f349481b03ddcf9ed2de0]:
  • @refinedev/cli@2.16.52

@refinedev/core@5.0.11

Patch Changes

• #7289 c040475723d8e2980c0b3ba6d8fae35e05525b09 Thanks @RonakRahane! - fix: useDeleteButton now passes meta params to useButtonCanAccess

  useDeleteButton was not forwarding the meta prop to useButtonCanAccess, which caused custom access control rules relying on meta to fail for delete buttons.

  Fixes #7285

@refinedev/cli@2.16.52

Patch Changes

• #7315 b319c8a7a2f11896008f349481b03ddcf9ed2de0 Thanks @Aaron3312! - fix: resolve bin path from cwd to support monorepo workspace hoisting

  resolveBin() now walks up from process.cwd() to find node_modules/.bin/<name>, fixing MODULE_NOT_FOUND errors when running refine dev in npm/bun/yarn workspaces where packages are hoisted to a parent node_modules.

@refinedev/remix-router@4.0.4

Patch Changes

• #7245 bf3cc65f73a6801a5fd1e42e6162efd2e89406d3 Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocation

  Increased qs.parse depth from default 5 to 10 to support deeply nested conditional filters (e.g., or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field], [operator], [value]) after page reload when using syncWithLocation: true.

@refinedev/react-router@2.0.4

Patch Changes

• #7245 bf3cc65f73a6801a5fd1e42e6162efd2e89406d3 Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocation

  Increased qs.parse depth from default 5 to 10 to support deeply nested conditional filters (e.g., or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field], [operator], [value]) after page reload when using syncWithLocation: true.

@refinedev/nextjs-router@7.0.5

Patch Changes

• #7245 bf3cc65f73a6801a5fd1e42e6162efd2e89406d3 Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocation

  Increased qs.parse depth from default 5 to 10 to support deeply nested conditional filters (e.g., or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field], [operator], [value]) after page reload when using syncWithLocation: true.

@refinedev/mui@8.0.1

Patch Changes

• #7266 91f0eac72e58fd220add066c12329d39bb38a326 Thanks @kaigritun! - fix(mui): prevent nested interactive elements in navigation buttons

@refinedev/core@5.0.10

Patch Changes

• #7245 bf3cc65f73a6801a5fd1e42e6162efd2e89406d3 Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocation

  Increased qs.parse depth from default 5 to 10 to support deeply nested conditional filters (e.g., or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field], [operator], [value]) after page reload when using syncWithLocation: true.