@refinedev/[email protected]

Patch Changes

• Updated dependencies [da9da4ed1a9700c7a48db6520d683168c48b226e, 451016a207d4dd6aecb4d56133efc1ad6229acff, da9da4ed1a9700c7a48db6520d683168c48b226e]:
  • @refinedev/[email protected]
  • @refinedev/[email protected]

@refinedev/[email protected]

Patch Changes

• #6354 da9da4ed1a9700c7a48db6520d683168c48b226e Thanks @arndom! - chore: bump express version to latest

  Bump express dependecy to ^4.21.0 to fix vulnerability in serve-static.

  Resolves #6321

@refinedev/[email protected]

Minor Changes

• #6330 5a81b35bc1eedbecb4b6c531a2fa5235dd0caf31 Thanks @alicanerdurmaz! - feat: add <Link /> component to navigate to a resource with a specific action. Under the hood, It uses useGo to generate the URL.

  Usage

  import { Link } from "@refinedev/core";
  
  const MyComponent = () => {
    return (
      <>
        {/* simple usage, navigates to `/posts` */}
        <Link to="/posts">Posts</Link>
        {/* complex usage with more control, navigates to `/posts` with query filters */}
        <Link
          go={{
            query: {
              // `useTable` or `useDataGrid` automatically use this filters to fetch data if `syncWithLocation` is true.
              filters: [
                {
                  operator: "eq",
                  value: "published",
                  field: "status",
                },
              ],
            },
            to: {
              resource: "posts",
              action: "list",
            },
          }}
        >
          Posts
        </Link>
      </>
    );
  };

  Fixes #6329

• #6330 5a81b35bc1eedbecb4b6c531a2fa5235dd0caf31 Thanks @alicanerdurmaz! - chore: From now on, useLink returns <Link /> component instead of returning routerProvider.Link.

  Since the <Link /> component uses routerProvider.Link under the hood with leveraging useGo hook to generate the URL there is no breaking change. It's recommended to use the <Link /> component from the @refinedev/core package instead of useLink hook. This hook is used mostly for internal purposes and is only exposed for customization needs.

  Fixes #6329

Patch Changes

• #6327 c630b090539082b5166b508053f87274624c794e Thanks @Anonymous961! - fix(core): added ability to return undefined to fallback to the default notification config when using the function form in successNotification and errorNotification props.

  Resolves #6270

• #6353 a0f2d7bbef3093e11c3024bb7fa2a0ffc3ce9e10 Thanks @alicanerdurmaz! - fix: The label and route fields in useMenu().menuItems were marked as deprecated, but they are not actually deprecated. This issue was caused by menuItems extending from IResourceItem, however, menuItems populates these fields and handles deprecation of these fields internally. This change removes the deprecation warning for these fields.

  export const Sider = () => {
    const { menuItems } = useMenu();
    menuItems.map((item) => {
      // these are safe to use
      console.log(item.label);
      console.log(item.route);
      item.children.map((child) => {
        // these are safe to use
        console.log(child.label);
        console.log(child.route);
      });
    });
  
    return <div>{/* ... */}</div>;
  };

  Fixes #6352

• #6386 bfe28f0316b3623aaef0b60ae39ebe24939dd0af Thanks @hugorezende! - fix(core): wrap setFilters and setSorters methods with useCallback to prevent looping re-renders

  With this we can use the setFilters as dependencies inside useEffects without infinite loop since state changes in the hook won't cause the functions to be re-assigned

  Fixes #6385

@refinedev/[email protected]

Patch Changes

• #6400 451016a207d4dd6aecb4d56133efc1ad6229acff Thanks @aliemir! - fix(cli): handle errors while fetching dependencies in get-project-type

  When working with deno or missing package.json file, an error was thrown while determining the project type. This was causing the CLI to crash even though the fallbacks were provided. This PR handles such errors in getProjectType and lets it use the fallback type.

  Resolves #6335

• #6354 da9da4ed1a9700c7a48db6520d683168c48b226e Thanks @arndom! - chore(cli): remove unused express dependency

  Removed express dependency which triggers a vulnerability warning from serve-static.

  Resolves #6321

• Updated dependencies [da9da4ed1a9700c7a48db6520d683168c48b226e]:

  • @refinedev/[email protected]

@refinedev/[email protected]

Patch Changes

• #6240 697561ba04abfb570ae978066668583096ea24c0 Thanks @pkarc! - fix(supabase): issue with parsed values when using conditional filters

  Fixed conditional filter's parsed values while using contains, containss, startswith and endswith.

  Fixes #6239

@refinedev/[email protected]

Minor Changes

• #6271 2b89fbd136b2134f22d38dff8d4a7f24e57e73db Thanks @Anonymous961! - feat(mui): added loading spinner to <Create />, <Edit /> and <Show /> components

  This change introduces a loading spinner to the <Create />, <Edit /> and <Show /> components in the @refinedev/mui package. The spinner provides a visual indication that data is being loaded, improving the user experience bym giving clear feedback during loading states.

  Resolves #5668

@refinedev/[email protected]

Patch Changes

• #6222 ec24fe0f37aa9b92991bf105719f6f42bb68d63c Thanks @Sergio16T! - feat: added support for meta.gqlVariables to hasura dataProvider. Updated GraphQLQueryOptions to include optional field gqlVariables

  Feat #5864

@refinedev/[email protected]

Patch Changes

• Updated dependencies [6963e591f8f307aee9362d5dfff99972eb64bf03, f5501f93a818d6e5811aa94cb354d77a2b1eb1ff]:
  • @refinedev/[email protected]
  • @refinedev/[email protected]

@refinedev/[email protected]

Patch Changes

• #6253 6963e591f8f307aee9362d5dfff99972eb64bf03 Thanks @aliemir! - chore(devtools-server): replace preferred-pm with package-manager-detector #6242

  preferred-pm has 24 dependencies: https://npmgraph.js.org/?q=preferred-pm
  package-manager-detector has no dependencies: https://npmgraph.js.org/?q=package-manager-detector

@refinedev/[email protected]

Patch Changes

• #6260 05b944a75f3a907c0df7b30591a5c5fbbc3cc3f7 Thanks @aliemir! - fix(core): useResourceParams not reflecting id prop changes immediately

  useResourceParams hook was not reflecting the changes in the id prop immediately. This was due to the id state being set in the useEffect hook. This PR fixes the issue by setting the id state properly during render rather than after the render is complete.

  Fixes #6259

• #6222 ec24fe0f37aa9b92991bf105719f6f42bb68d63c Thanks @Sergio16T! - feat: added support for meta.gqlVariables to hasura dataProvider. Updated GraphQLQueryOptions to include optional field gqlVariables

  Feat #5864