Giter VIP home page Giter VIP logo

Comments (6)

nicolasschabram avatar nicolasschabram commented on May 22, 2024 2

I ended up with this by the way:

function revalidate(matcher: string | RegExp) {
  cache
    .keys()
    .filter(key => key.match(matcher))
    .forEach(key => mutate(key));
}

from swr.

nicolasschabram avatar nicolasschabram commented on May 22, 2024 1

I just saw that #78 is kinda related. Feel free to close if it's the same thing!

from swr.

shuding avatar shuding commented on May 22, 2024 1

Yeah accepting glob pattern or RegExp is a good idea, but it will be unnecessary to add it as an option after giving you the full control of the cache.

from swr.

sergiodxa avatar sergiodxa commented on May 22, 2024 1

I think this could now be solved with the exposed cache, get all cache keys, filter based on a glob and then call mutate against them without data to revalidate them or call cache.delete to delete them altogether

from swr.

shuding avatar shuding commented on May 22, 2024 1

I think 'trigger' is s feature not directly related to the cache. As a library user I would like to be able to call 'trigger' without necessarily knowing how the cache works internally.

I like your take @JulianG and this is also my opinion about why I personally don't want cache APIs to be documented for now. Because ideally they should be covered by some other high level APIs or plugins. It's dangerous for end users to touch the cache.

(I'd close this PR, it's kinda unrelated to the topic)

from swr.

JulianG avatar JulianG commented on May 22, 2024

Hello!

I think I see the point in not bloating the library with features that can be done by combining the existing feature set, but

I don't think we can rely on the exposed cache for this: (let me know if I'm wrong) (I was wrong)

You may want to only revalidate "active" or visible queries only. For example, if I update "/users/42" and now I want to revalidate also "/users/", "/users/42" and any other "visible" users but not every user in the cache. Assuming other users would still be revalidated when/if they're requested again.

Also it may not be desirable to rely on the cache for this: (this is just opinion)

I think 'trigger' is s feature not directly related to the cache. As a library user I would like to be able to call 'trigger' without necessarily knowing how the cache works internally.

from swr.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.