@refinedev/core 4.8.5 → 4.9.0

package/CHANGELOG.md

@@ -1,5 +1,62 @@
 # @pankod/refine-core
 
+## 4.9.0
+
+### Minor Changes
+
+-   [#4135](https://github.com/refinedev/refine/pull/4135) [`e72c0d2b41f`](https://github.com/refinedev/refine/commit/e72c0d2b41ffcd9d5853e0d912a31cb88fab9841) Thanks [@salihozdemir](https://github.com/salihozdemir)! - feat: Expose the query params to the `meta` and add the ability to pass global `meta` to data provider methods
+
+    -   Added the ability to pass `meta` to data provider methods globally for specific resources.
+
+        For example, to pass the `role` property to all data provider methods for the `posts` resource, use the following code:
+
+        ```tsx
+        import { Refine } from "@refinedev/core";
+
+        const App: React.FC = () => {
+            return (
+                <Refine
+                    resources={[
+                        {
+                            name: "posts",
+                            meta: {
+                                role: "editor",
+                            },
+                        },
+                    ]}
+                />
+            );
+        };
+        ```
+
+        Now, when you call any data hook with the `posts` resource, the `meta` property will be accessible in the data provider methods.
+
+        ```tsx
+        const dataProvider = {
+            getList: async ({ resource, meta }) => {
+                console.log(meta.role); // "editor"
+            },
+        };
+        ```
+
+    -   Added the query params to the `meta` property by default.
+
+        For example, if you call the `useList` hook on the `example.com/posts?status=published` URL, the `meta` property will be accessible in the data provider methods as follows:
+
+        ```tsx
+        const dataProvider = {
+            getList: async ({ resource, meta }) => {
+                console.log(meta.status); // "published"
+            },
+        };
+        ```
+
+### Patch Changes
+
+-   [#4159](https://github.com/refinedev/refine/pull/4159) [`f7f590589e7`](https://github.com/refinedev/refine/commit/f7f590589e78a255f2ce292311c6bae765b9de8f) Thanks [@aliemir](https://github.com/aliemir)! - fixed: missing resource meta in route compositions
+
+    Added missing resource meta values when composing routes. This fixes the bug where the resource meta values does not included in the route composition.
+
 ## 4.8.5
 
 ### Patch Changes

package/dist/definitions/helpers/router/compose-route.d.ts

@@ -1,4 +1,4 @@
-import { MetaDataQuery, ParseResponse } from "../../../interfaces";
+import { MetaQuery, ParseResponse } from "src/interfaces";
 /**
  * This function will compose a route with the given params and meta.
  * - A route can have parameters like (eg: /users/:id)
@@ -6,5 +6,5 @@ import { MetaDataQuery, ParseResponse } from "../../../interfaces";
  * - Then we prepare the route params with the given params and meta (eg: { id: 1 })
  * - Then we replace the route params with the prepared route params (eg: /users/1)
  */
-export declare const composeRoute: (designatedRoute: string, params?: ParseResponse, meta?: MetaDataQuery) => string;
+export declare const composeRoute: (designatedRoute: string, resourceMeta?: MetaQuery, parsed?: ParseResponse, meta?: Record<string, unknown>) => string;
 //# sourceMappingURL=compose-route.d.ts.map

package/dist/definitions/helpers/router/compose-route.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"compose-route.d.ts","sourceRoot":"","sources":["../../../../src/definitions/helpers/router/compose-route.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAKnE;;;;;;GAMG;AACH,eAAO,MAAM,YAAY,oBACJ,MAAM,WACf,aAAa,SACf,aAAa,KACpB,MAaF,CAAC"}
+{"version":3,"file":"compose-route.d.ts","sourceRoot":"","sources":["../../../../src/definitions/helpers/router/compose-route.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAC;AAI1D;;;;;;GAMG;AACH,eAAO,MAAM,YAAY,oBACJ,MAAM,iBACT,SAAS,WACf,aAAa,SACf,OAAO,MAAM,EAAE,OAAO,CAAC,KAC9B,MAwBF,CAAC"}

package/dist/definitions/helpers/router/prepare-route-params.d.ts

@@ -1,9 +1,8 @@
-import { MetaDataQuery, ParseResponse } from "../../../interfaces";
 /**
  * Prepares the route params by checking the existing params and meta data.
  * Meta data is prioritized over params.
  * Params are prioritized over predetermined id, action and resource.
  * This means, we can use `meta` for user supplied params (both manually or from the query string)
  */
-export declare const prepareRouteParams: <TRouteParams extends Record<string, string | number | Symbol | undefined> = Record<string, string | number | Symbol | undefined>>(routeParams: (keyof TRouteParams)[], params?: ParseResponse, meta?: MetaDataQuery) => Partial<TRouteParams>;
+export declare const prepareRouteParams: <TRouteParams extends Record<string, unknown> = Record<string, unknown>>(routeParams: (keyof TRouteParams)[], meta?: Record<string, unknown>) => Partial<TRouteParams>;
 //# sourceMappingURL=prepare-route-params.d.ts.map

package/dist/definitions/helpers/router/prepare-route-params.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prepare-route-params.d.ts","sourceRoot":"","sources":["../../../../src/definitions/helpers/router/prepare-route-params.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAEnE;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB,mLAOnB,aAAa,SACf,aAAa,0BAetB,CAAC"}
+{"version":3,"file":"prepare-route-params.d.ts","sourceRoot":"","sources":["../../../../src/definitions/helpers/router/prepare-route-params.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB,uHAIrB,OAAO,MAAM,EAAE,OAAO,CAAC,0BAShC,CAAC"}