Update hooks.ts lastsubmission to accept null value #292
Conversation
|
Hi @zifahm, I would like to learn more about your usecase first. Can you tell me more what you are trying to do? That will help me understand your problem and identify if there is a better solution :) |
|
I don't always use "conform" for all of my forms. I might also return "json(null)" frequently when I simply need to execute an action. However, TypeScript's type checking becomes problematic when using "json(null)" instead of "json(undefined)," and strangely, using "json(undefined)" doesn't trigger the loader to refresh for some reason. This is the scenario I'm dealing with. As for my current workaround, I use the following code snippet: lastSubmission: lastSubmission === null ? undefined : lastSubmissionI really don't want to have to do this repeatedly. Therefore, allowing "conform" to accept "null" values would reduce the amount of code I need to write. |
In Remix, there may be times when you need to return JSON(null), which is often what Remix expects. If you return JSON(undefined), the loaders are not refetched. To resolve this issue, accepting null for "lastsubmission" keeps TypeScript happy and ensures the loader is refetched.
In Remix, there may be times when you need to return json(null), which is often what Remix expects. If you return json(undefined), the loaders are not refetched. To resolve this issue, accepting null for "lastsubmission" keeps TypeScript happy and ensures the loader is refetched.