reatomUseContext #797

artalar · 2023-07-18T20:00:43Z

artalar
Jul 18, 2023
Maintainer

In the React world, it is a common pattern and the main mindset to bind a state lifetime to a component lifetime. It is a good pattern because of its obvious memory management benefits - all data is automatically cleared on unmount.

If you are trying to use this pattern with Reatom (or any other global state manager), you could have a set of confusions: you need to use useAtom with a primitive and share the created atom via props, which could take a lot of boilerplate - prop drilling and extra explicit type definitions for all props of intermediate components. Or, you should create a context and manage the whole thing yourself.

To simplify this case, I propose a new method reatomUseContext with a couple of handy overloads, which is creates an atom for the provider mount and destroy it on unmount.

// definition
const useData = reatomUseContext(initState);

// instantiation
const DataPage = () => (
  <useData.Provider>
    <DataComponent />
  </useData.Provider>
);

// definition
const useData = reatomUseContext<Data>();

// instantiation
const DataPage = ({ data }) => (
  <useData.Provider value={data}>
    <DataComponent />
  </useData.Provider>
);

// usage
const DataComponent = () => {
  const [data, setData, dataAtom] = useData();
};

// usage
const DataComponent = () => {
  const [some] = useData((ctx, state) => state.some);
};

Of course it should be possible to use reatomUseContext for a whole model creation.

// definition
const usePomodoro = reatomUseContext(({ interval }) => {
  const pomodoroAtom = reatomTimer({ interval });

  return { pomodoroAtom };
});
// instantiation
const PomodoroPage = ({ interval }) => (
  <usePomodoro.Provider init={{ interval }}>
    <DataComponent />
  </usePomodoro.Provider>
);

// usage
const PomodoroProgress = () => {
  const [progress] = usePomodoro((ctx, { pomodoroAtom }) =>
    ctx.spy(pomodoroAtom.progressAtom)
  );
};

nikitaprokopov · 2024-04-24T05:02:21Z

nikitaprokopov
Apr 24, 2024

Example of code, that I am writing without this feature:

import { withStatusesAtom, withErrorAtom, withDataAtom, reatomAsync, withAbort, atom } from "@reatom/framework";
import { fetchUserProfile } from "@/api";

export function createUserProfileModel() {
  const fetchUserProfileAction = reatomAsync(async (ctx) => {
    const profile = await ctx.schedule(() => fetchUserProfile({ controller: ctx.controller }));

    return {
      ...profile,

      context: {
        jobDescriptionAtom: atom(profile.context.cv, "jobDescriptionAtom"),
        cvAtom: atom(profile.context.job_description, "cvAtom"),
      },
    };
  }, "fetchUserProfileAction").pipe(withDataAtom(), withAbort(), withErrorAtom(), withStatusesAtom());

  return {
    fetchUserProfileAction,
  };
}

import type { ReactNode } from "@tanstack/react-router";

import { createContext, useMemo } from "react";

import { createUserProfileModel } from "./user-profile-model";

export const UserProfileModelContext = createContext<ReturnType<typeof createUserProfileModel> | null>(null);

export function UserProfileModelProvider({ children }: { children: ReactNode }) {
  const userProfileModel = useMemo(() => createUserProfileModel(), []);
  return <UserProfileModelContext.Provider value={userProfileModel}>{children}</UserProfileModelContext.Provider>;
}

import { useContext } from "react";

import { UserProfileModelContext } from "./user-profile-context";

export function useUserProfileModel() {
  const userProfileModel = useContext(UserProfileModelContext);

  if (userProfileModel === null) {
    throw new Error("useContext must be used within a UserProfileModelProvider");
  }

  return userProfileModel;
}

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

reatomUseContext #797

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

reatomUseContext #797

Uh oh!

Uh oh!

artalar Jul 18, 2023 Maintainer

Replies: 1 comment

Uh oh!

nikitaprokopov Apr 24, 2024

artalar
Jul 18, 2023
Maintainer

nikitaprokopov
Apr 24, 2024