Feature request: $cache

[j-greig]

For use with $fetch :)

[SimoTod]

Thanks for suggesting it @j-greig.
Could you post an example of how you immagine the feature to work?

[KevinBatdorf]

Another thing we could probably solve from that demo is the x-for + $parent relationship.

I used x-init="$nextTick(() => loadCoin($parent.coins[$el.__x_for_key]))" to grab the outer component data after the key is set, which isn't very user friendly.

[SimoTod]

Yeah, the demo seems a bit complex because of the Alpine limitation when using x-for and nested x-data. There are simpler ways without using nested x-data but it's not the point of the thread.
I was just worried that a lot of users will get confused if we provide too many options and things to configure (for example, what would it be a sensible value for seconds? 10? 30? 60? It's probably better to have something to invalidate the cache so users can use it on actions or watcher like your last example if they really need to)

[KevinBatdorf]

For $cache yeah let's see what you come up with first. I've been working with Laravel Cache this weekend and trying various warming strategies so that api is fresh in my head. ie.Cache::put('key', 'value', $seconds = 10);

But I would probably have it default to "forever" for our helper so there's no overhead, and just give the user the option to override it. We can add that later though if there's demand for it

[SimoTod]

@j-greig in the meantime, this example should do the same trick without calling fetch every time: https://codepen.io/SimoTod/pen/YzpZPMJ

[KevinBatdorf]

That's a good optimization. Makes the naming for a helper for $el.__x_for_key more obvious as $currentKey too, which would replace the title in that demo: <p x-text="$el.__x_for_key"></p>

updated: https://codepen.io/KevinBatdorf/pen/XWNpvrm

We'd have to wait for it to be available though too.

[SimoTod]

Moved to discussions since it's not an actual bug but a feature request.