A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility.
MIT License
Bot releases are visible (Hide)
Published by refine-bot about 1 year ago
6ab41f88343
Thanks @MahirMahdi! - Now useCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.Published by refine-bot about 1 year ago
6ab41f88343
Thanks @MahirMahdi! - Now useCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.Published by refine-bot about 1 year ago
6ab41f88343
Thanks @MahirMahdi! - Now useCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.Published by refine-bot about 1 year ago
6ab41f88343
Thanks @MahirMahdi! - Now useCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.Published by refine-bot about 1 year ago
#5050 613af0021f6
Thanks @alicanerdurmaz! - feat: pass dataProviderName
to liveProvider.subscribe
method.
From now on, you can use dataProviderName
to distinguish between different data providers in live provider.
Refer to documentation for more info about multiple data providers ->
import { useForm, useList } from "@refinedev/core";
useList({
dataProviderName: "first-data-provider",
});
useForm({
dataProviderName: "second-data-provider",
});
import { LiveProvider } from "@refinedev/core";
export const liveProvider = (client: any): LiveProvider => {
return {
subscribe: ({
channel,
types,
params,
callback,
dataProviderName,
}) => {
console.log({ dataProviderName }); // "second-data-provider"
},
};
};
#5053 857d4020a30
Thanks @alicanerdurmaz! - feat: The parameter types of data provider methods have been exported.
From now on, you can use the parameter types of Data Provider methods.
import type {
DataProvider,
GetListResponse
// new exported types
GetListParams,
GetManyParams,
GetOneParams,
CreateParams,
CreateManyParams,
UpdateParams,
UpdateManyParams,
DeleteOneParams,
DeleteManyParams,
CustomParams,
} from "@refinedev/core";
const myDataProvider: DataProvider = {
getList: async (params: GetListParams): Promise<GetListResponse<any>> => {
return { data: [], total: 0 };
},
};
Published by refine-bot about 1 year ago
7533e541739
Thanks @pull! - Fixed the issue with conflicting devtools port when PORT
environment variable is set.Published by refine-bot about 1 year ago
#26 7533e541739
Thanks @pull! - Use the proper devtools url coming from the websocket handshake rather than using the hardcoded port.
Updated dependencies [7533e541739
, 7533e541739
]:
Published by refine-bot about 1 year ago
#26 7533e541739
Thanks @pull! - feat: From now on, npm run refine devtools init
updates @refinedev/core
to latest version.
Updated dependencies [7533e541739
]:
Published by refine-bot about 1 year ago
1fa531ebe89
Thanks @aliemir! - Fixed the issue with conflicting devtools port when PORT
environment variable is set.Published by refine-bot about 1 year ago
#5056 1fa531ebe89
Thanks @aliemir! - Use the proper devtools url coming from the websocket handshake rather than using the hardcoded port.
Updated dependencies [68f24d5b596
, 1fa531ebe89
]:
Published by refine-bot about 1 year ago
#5055 68f24d5b596
Thanks @alicanerdurmaz! - feat: From now on, npm run refine devtools init
updates @refinedev/core
to latest version.
Updated dependencies [1fa531ebe89
]:
Published by refine-bot about 1 year ago
#5040 ca57048580a
Thanks @IkumaTadokoro! - fix: issue with #4972
When using the Hasura provider with the 'graphql-default' naming convention, snake-case graphql operators (e.g. _is_null) were not converted to the correct case, causing query errors.
This problem is now fixed. Now the snake_case operator is converted according to the given naming convention (e.g. hasura-default: _is_null, graphql-default: _isNull).
Published by refine-bot about 1 year ago
#5034 85bcff15d1e
Thanks @alicanerdurmaz! - feat: The go
function returned by useGo
now accepts a resource
object as the to
parameter.
From now now, you can provide either a string or a resource object to the go
function. When a resource object is passed, it will be transformed into the path defined within the resources array of the <Refine />
component.
to
accepts an object with the following shape to navigate to a resource:
Name | Type | Description |
---|---|---|
resource | string |
resource name or identifier. |
id | [BaseKey ][basekey] |
required when action is "edit" , "show" , or "clone" . |
action |
"list" | "create" | "edit" | "show" | "clone"
|
action name. |
import { useGo } from "@refinedev/core";
const MyComponent = () => {
const go = useGo();
return (
<Button
onClick={() => {
go({
to: {
resource: "posts", // resource name or identifier
action: "edit",
id: "1",
}
query: {
foo: "bar",
},
type: "push",
});
}}
>
Go Posts With Default Filters
</Button>
);
};
Published by refine-bot about 1 year ago
fba8f737005
Thanks @saarthak08! - fix: headers persisting in useCustomMutation hookPublished by refine-bot about 1 year ago
847124858e0
Thanks @dzcpy! - fix: added types
path to export in package.json
Published by refine-bot about 1 year ago
#5026 a605e4cd318
Thanks @alicanerdurmaz! - feat: deprecated <ThemedLayout />
and <Layout />
components removed from swizzle
.
From now on, users can swizzle <ThemedLayoutV2 />
component instead.
feat: swizzled <ThemedLayoutV2 />
component destination changed to src/components/layout/
from src/components/themedLayout
.
#4974 a7b32dbf137
Thanks @IkumaTadokoro! - fix: add missing DataGrid operator conversion cases
MUI defines the operator for each column types in here. However, there were not enough conversion cases for the following operators, so this changes added them to the mapping.
Published by refine-bot about 1 year ago
#5026 a605e4cd318
Thanks @alicanerdurmaz! - feat: deprecated <ThemedLayout />
and <Layout />
components removed from swizzle
.
From now on, users can swizzle <ThemedLayoutV2 />
component instead.
feat: swizzled <ThemedLayoutV2 />
component destination changed to src/components/layout/
from src/components/themedLayout
.
Published by refine-bot about 1 year ago
#5026 a605e4cd318
Thanks @alicanerdurmaz! - feat: deprecated <ThemedLayout />
and <Layout />
components removed from swizzle
.
From now on, users can swizzle <ThemedLayoutV2 />
component instead.
feat: swizzled <ThemedLayoutV2 />
component destination changed to src/components/layout/
from src/components/themedLayout
.
Published by refine-bot about 1 year ago
#5026 a605e4cd318
Thanks @alicanerdurmaz! - feat: deprecated <ThemedLayout />
and <Layout />
components removed from swizzle
.
From now on, users can swizzle <ThemedLayoutV2 />
component instead.
feat: swizzled <ThemedLayoutV2 />
component destination changed to src/components/layout/
from src/components/themedLayout
.
Published by refine-bot about 1 year ago
#5022 80513a4e42f
Thanks @BatuhanW! - chore: update README.md
#5024 1bb29d9fc3d
Thanks @aliemir! - Added dynamic announcements to the CLI to show when a command is executed. Users will be able to receive news and updates about refine without having to update their dependencies.
Updated dependencies [80513a4e42f
, 20f5b6128d4
]: