🐛 Fix(web): invalid type errors when creating someday event (#615)

* fix(web): make `_id`optional

a someday event does not have an `_id` when we are drafting/creating a new one

* fix(web): set default order for new events to pass validation

Updated the `useSidebarActions` hook to assign a default order of -1 to new events, ensuring they pass Zod validation during creation.

Author: that-one-arab

packages/web/src/common/types/web.event.types.ts

@@ -15,7 +15,6 @@ export const GridEventSchema = CoreEventSchema.extend({
 });
 
 export const SomedayEventSchema = CoreEventSchema.extend({
-  _id: z.string(),
   order: z.number(),
   isSomeday: z.literal(true),
 });

packages/web/src/views/Calendar/components/Draft/sidebar/hooks/useSidebarActions.ts

@@ -373,6 +373,10 @@ export const useSidebarActions = (
     if (!event) return;
 
     let _event = { ...event };
+    // We need to provide it to pass zod validation.
+    // Order is already corrected after the event is submitted
+    // so its okay to provide any random int (hence -1)
+    _event.order = -1;
 
     if (!_event.startDate || !_event.endDate) {
       // This probably means we are creating a new event, hence why we don't have start/end dates