You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe just redefine how we're doing events? Right now I'm kind of just saying info can be ANY object. Maybe we can just think of it as notes for now. Events seem to have one commonality which is they all have a name, a date it occurred. Some have similarities like duration. You may arc or hangboard both for a duration, but I don't think they're really the same duration, hangboarding is seconds and ARCing is minutes... Should we just have multiple different Types of events with specific data for each? Even if this is true, it still needs to fulfill the schema for events...
The text was updated successfully, but these errors were encountered:
I really want this object to just have anything in it so I can put whatever Data I want for specific events. Would be interested in thinking more deeply about this typing since its actually really bad. Anyways, heres some resources I was looking at but could never really get it to work. Something about the Json adding a null and passthrough not being valid against that https://github.com/colinhacks/zod#json-type. colinhacks/zod#2178
Might not be a huge issue right now. OutdoorMileage component just parses the JSON string. Still not ideal but not super necessary. If you are able to get JSON objects, then update the places we parse and stringify as part of the story
Maybe just redefine how we're doing events? Right now I'm kind of just saying info can be ANY object. Maybe we can just think of it as notes for now. Events seem to have one commonality which is they all have a name, a date it occurred. Some have similarities like duration. You may arc or hangboard both for a duration, but I don't think they're really the same duration, hangboarding is seconds and ARCing is minutes... Should we just have multiple different Types of events with specific data for each? Even if this is true, it still needs to fulfill the schema for events...
The text was updated successfully, but these errors were encountered: