GithubHelp home page GithubHelp logo

Comments (3)

davidmccabe avatar davidmccabe commented on May 8, 2024 12

We are planning some memory management improvements where atomFamily and selectorFamily will forget when Recoil itself does. At the moment they are just simple implementations of memoization, equivalent to what you might do yourself. We plan to roll out better memory management soon.

from recoil.

Bruno-Tavares-Bose avatar Bruno-Tavares-Bose commented on May 8, 2024 3

Regarding this point, make sense to have a delete operation? Like we have the get/set/reset.

Follow me on my thought please:
Imagine we have an atom that is a list (todo for example), and we have an atomFamily that is an item on that list.
we could create a selector for our list like so:

const todoAtom = atom({
  key: 'todoAtom',
  default: []
});
const todoItemAtom = atomFamily({
  key: 'todoItemAtom',
  default: {
    label: 'todo item',
    completed: false
  }
});
const todoState = selector({
  key: 'todoState',
  get: ({ get }) => get(todoAtom),
  set({ get, set, delete }, { type, payload }) {
    let todo = get(todoAtom);

    switch(type) {
      case ADD_ITEM:
        todo = [...todo, uuid()];
        break;
      case REMOVE_ITEM:
        todo.filter((id) => id !== payload.id);

        delete(todoItemAtom(payload.id));
        break;
      default:
        return;
    }

    set(todoAtom, todo);
  }
});

☝️ make sense the delete? And, is this a "correct" approach for a list of items?

Thanks in advance and awesome work mates, being testing and it feels good :)

from recoil.

acutmore avatar acutmore commented on May 8, 2024

Hi @jamiebuilds There is some information about this in #30 (comment) and #23 (comment)

We are adding a feature soon where atoms will be deleted when no longer used, together with another hook that lets a component retain an atom without subscribing to it. These could be combined into a utility that gives you a list of IDs with automatic deletion of the individual atoms when they are removed from the list.

Currently you have to use the useResetRecoilState hook to delete atoms.

To make a family of atoms, just create a memoized function that returns a distinct atom for each state
[snip]
We are going to open-source a utility called atomFamily/selectorFamily that does this for you in the near future.

Sounds like selectorFamily has built in memoization. https://recoiljs.org/docs/api-reference/utils/selectorFamily

from recoil.

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.