Post

Question for #Laravel devs: how do you avoid duplicated queries when you're listing the same model in both nav & footer blade components?

27/8/25, 3:16 pm0 reposts1 like

void 🌖

@leloup.dev

27 Aug 2025

I just tried the once() function (for memoization) but it seems like it's still executing the query twice.

Lau Bannenberg

@lau-b.bsky.social

27 Aug 2025

The docs say that if you use once() from within an object instance, it'll be "once for that instance", not once globally, that might be the reason?

void 🌖

@leloup.dev

27 Aug 2025

Ah, missed that, good catch! Yeah that's definitely it.

Tim Van Dijck

@veedee.dev

28 Aug 2025

I think it's overkill for most apps, but you could use a singleton: gist.github.com/timvandijck/... Alternatively you can make the singleton class typed instead of generic with a getter/setter like I did.

gist.github.comSharing data across views/componentsSharing data across views/components. GitHub Gist: instantly share code, notes, and snippets.

void 🌖

@leloup.dev

28 Aug 2025

That’s clean! Thanks for the example

Muhammed Sarı

@handle.invalid

28 Aug 2025

An identity map would be the optimal solution for this problem. Too bad it's never going to land in Eloquent 😞 github.com/laravel/fram...

void 🌖

@leloup.dev

28 Aug 2025

Ohhh that’s super interesting! Maybe there’s a way to package that up?

Muhammed Sarı

@handle.invalid

28 Aug 2025

I'm afraid that'll be an impossible task as you need to hook into the framework core in order to set the map at the right times. That'd be impossible to do in a separate package. Well, maybe not impossible but it would make it much harder than it needs to be, I reckon.