Hello @itaysmalia, thanks for the bug report.

I'm sorry for your trouble, the last thing we want while developing is to introduce breaking changes in minor or patch versions.

The reason I added that id check in this PR is that id was already required on the TypeScript in previous versions. Are you using JavaScript?

Hi @alicanerdurmaz!
thanks for responding this fast...
Looks like my explanation wasn't detailed enough 😅
I am using typescript, and I am passing an empty string as the id, something like this:

const {...} = useForm({id: '', ...});

and typescript allowed it...
The problem is probably because !"" evaluates to true then the "missing id" error is thrown.
I am using an empty string because in strapi-v4 data provider the id part of the api requests is empty, then then the path ends with ...<resource>/ and it works with the single types rest api paths of strapi.
The possible solution might be checking for null/undefined value in this if statement...
Thank you very much!

Hello again @itaysmalia, thank you for the detailed explanation!

You're absolutely right, the mentioned PR introduced a breaking change due to a bug. We're targeting the December release to address this issue.

Here's how it should have been handled:
7e71f12#diff-85aeb33cfc5f222b2eca2e2667b6c2ac7a7c639e6f32cdb8c74abc34bde20e5eR324

- if (!id) throw missingIdError;
+ if (typeof id === "undefined") throw missingIdError;

We also believe that making the ID optional is the right approach, but implementing this change affects several parts of the core. We plan to introduce this improvement with Refine 5.