@sethmills21@twodayslate@sarunw This was super confusing to me too. Some things that have worked:
- contentShape(.rect)
- .frame(maxWidth: .infinity)
Sometimes you have to also remove the default button styling. It is a steep learning curve.
@louzell_@sethmills21@sarunw Also if you initialize it as a @State param it will only initialize once. I have a ViewModelsProviderView where I init all my view models as state and then pass them through the environment. Then any child class can access it
@romainhuet@latentsauce For parsing certain types of content (photos of calendars etc.) I’ve seen gpt-4o get the dates off by one. I’d been hoping to be able to fine tune a model to handle these cases
Just spent 7 hours debugging something only to realize it was broken because a dependency got upgraded and introduced a bug.
It’s yours Devin, I don’t even want it!
@fredkisss@AdamRackis Checking auth inside of RSCs is fine though. It’s client components rendering on the server which you’d have the same issue with regardless of where the BE is
@fredkisss@AdamRackis Yup, it’s all working well now, just similar to server actions being serial, it’s a major foot gun that isn’t referenced in the docs very well. There are a lot of docs about how fetch requests are auto cached etc. but nothing that explains what has to be a pretty common use case
@fredkisss@AdamRackis Yea, in the browser it’s fine though, the http only cookies will get sent with the fetch request automatically. In SSR, they won’t, which is where I’d use cookies() to manually forward it along.
@fredkisss@AdamRackis Yea, that’s a good idea. Just an annoying extra hop to work around some artificial boundaries (not being able to import `cookies` from a client component). The work around I have now of just prefetching in the server component works well too and avoids the extra hop