@NicoleTrumper1 Some folks reported a while back that ads were getting inserted in the middle of the puzzle. Is there anything broken like that happening for you with ads?
@anbasu I was just made aware of this problem. I'm working on figuring it out. I made some changes, and it looks like there are some side effects from that. Apologies for the trouble!
@joelnet I think yeah, you're missing out. My team started using it. Now instead of writing a lot of blocks of code and comments (oh, the comments) ourselves, we spend that same amount of time talking about how surprisingly good Copilot is.
@joncoopertweets It depends. International or domestic? TSA Pre-Check or not? How difficult and far away is parking? Any bags to check? Too many variables for a simple answer.
@madzadev I'm the type of developer who thinks: "Why is it called printType when it isn't printing the type? It should be called getType." π Then after I've overcome that obstacle, I'd consider the team's style guide and use the team's preference. Sans a team, I'd use D. Short and sweet.
@riverchic66 Sorry this is happening to you! Unfortunately there's an iOS bug that causes that periodically, and despite extensive investigation and trial & error, I've yet to discover the root cause or a solution. π’
@ifeanyi_@kentcdodds@remix_run@jimniels Ah, you got me inspecting it more closely. Actually, if I redirect back to / after logging in, the user is fine in context, but when the index page redirects in loader(), that's when the user in context is initially stale. That redirect is what seems to be my issue.
@ifeanyi_@kentcdodds@remix_run@jimniels This is basically the approach I'm taking. Root's loader() returns the user (via cookie), with its component providing it to a UserProvider context wrapping the Outlet. Problem is the context is always stale immediately after a login until the next time its loader() is called.