Ali Emir Şen

Hey @vitali-bc, sorry for the issue! Looks like our `swizzle` command had some issues with the `import type` statements which are introduced with the latest release to our codebase. I've...

Hey @pcfreak30, thank you for the issue. We'll disable the minification and also update our build process to export individual files instead of bundling them into a single file. This...

Hey @klasjersevi thank you for the issue! Refine's `notificationProvider` designed to handle notifications shown by Refine's hooks and components and those were the types we use in Refine. It will...

Hey @soranoo, thank you for the request. Looks like we're also missing `startswiths`, `endswiths`, can you include them in your implementation? I'm assigning the issue to you and we'll be...

Thank you for reporting @pkarc, we'll review the PR as soon as we can 🚀

Hey @reedwane, thank you for the issue! I think we should definitely have this feature. Do you think having a generic type for the component can improve the DX? Something...

Hey @noritsune, any updates on this one? We'll be happy to help if you have any issues 🙏

Hey @noritsune sorry for the late response. Thank you for the explanation. I also think that top-level ordering can be the default but it will require a major version update...

Looks like there's an issue with the types here. When passing `successNotification` or `errorNotification` props as functions, the type allows returning `OpenNotificationParams` or `false` but actually you can also pass...

@PercivalFigaro I've also noticed that when we use `@ts-ignore` or `@ts-expect-error` directives in `useForm` hook props, it breaks the generics and this also breaks the return type (for this case...