React Context Provider中的过时关闭

如何解决React Context Provider中的过时关闭

我有一个React Native应用程序,我想在其中创建一种启用/禁用来自应用程序流中多个位置的通知的方法。启用通知还涉及保留一些取消订阅处理程序,这些处理程序应在禁用期间进行适当的清理。它还需要写入/读取react-redux存储。

为此,我创建了一个上下文,以与应用程序中的任意组件共享功能。您可以在下面看到简化版本。

我似乎遇到了过时的关闭问题,我不知道如何正确解决。我添加了注释,以解释代码中的内联问题。

如果这是错误的方法,那么我也将对如何更好地解决指定的用例产生深刻的见解。

interface NotificationContextProps {
  enableNotifications: (promptForPermission: boolean) => Promise<void>;
  disableNotifications: () => void;
}

const SharedNotificationContext = React.createContext<NotificationContextProps>({
  enableNotifications: async () => {/**/},disableNotifications: () => {/**/},});

export const SharedNotificationProvider: FunctionComponent = ({children}) => {
  const notificationListenerUnsub = useRef(() => {/**/});
  const tokenRefreshListenerUnsub = useRef(() => {/**/});

  // PROBLEM: Would have liked to use `useState` here instead of useRef
  // but the value change never reflected in the functions using the value.
  // Probably same stale closure issue as the other PROBLEM.
  const isEnabled = useRef(false);

  // PROBLEM: When udating the state with the `registerToken` function,this gets
  // updated correctly. When I place a `console.log(existingDeviceToken);` below this,// I can see that the change propagates here correctly.
  // BUT the `registerDeviceToken` function which does a check if the token changed,// (called by `enableNotifications` which is called on every app state change)
  // still uses the "old" `existingDeviceToken value` for the comparison
  const existingDeviceToken = useSelector((state: any) => state.firebase.token);

  const dispatch = useDispatch();
  const registerToken = (token: string) => dispatch({ type: FirebaseEvents.TOKEN,payload: token });

  const registerDeviceToken = async () => {
    const deviceToken = await getFirebaseToken();

    // PROBLEM: Even though the `existingDeviceToken` changed,// it's still using the old value.
    if (deviceToken && deviceToken !== existingDeviceToken) {
      registerToken(deviceToken);
    }
  };

  const enableNotifications = async (promptForPermission: boolean) => {
    const permissionStatus = await getPushPermission(promptForPermission);

    if (permissionStatus.hasPermission && !isEnabled.current) {
      // Has Push Permissions & Listeners have not yet been setup
      cleanupNotificationHandlers();
      await registerDeviceToken();
      await updateNotificationListeners();
      isEnabled.current = true;
    } else if (permissionStatus.hasPermission && isEnabled.current) {
      // Has Push Permissions but Listeners already exist
      await registerDeviceToken();
    } else if (permissionStatus.authStatus === messaging.AuthorizationStatus.DENIED) {
      // Push Permissions were declined or removed
      disableNotifications(true);
    }
  };

  const disableNotifications = async (permissionsDeclined: boolean) => {
    await removeFirebaseToken();
    registerToken("");
    cleanupNotificationHandlers();
    isEnabled.current = false;
  }

  const updateNotificationListeners = async () => {
    // Create listener and store the unsub function (simplified for demo)
    notificationListenerUnsub.current = () => {};
    tokenRefreshListenerUnsub.current = () => {};
  };

  const cleanupNotificationHandlers = () => {
    notificationListenerUnsub.current();
    notificationListenerUnsub.current = () => {/**/};
    tokenRefreshListenerUnsub.current();
    tokenRefreshListenerUnsub.current = () => {/**/};
    isEnabled.current = false;
  };

  return (
    <SharedNotificationContext.Provider value={{ 
      enableNotifications,disableNotifications 
    }}>
      {children}
    </SharedNotificationContext.Provider>
  );
};

export const useNotifications = () => {
  return React.useContext(SharedNotificationContext);
};

我已经厌倦了用useCallback包裹函数,像这样:

const registerDeviceToken = useCallback(async () => {/**/},[existingDeviceToken]);
const enableNotifications = useCallback(async (promptForPermission: boolean) => {/**/},[registerDeviceToken]);

但这没有帮助。

有效的方法是将existingDeviceToken打包到useRef中,然后使用

useEffect(() => {existingDeviceTokenRef.current = existingDeviceToken},[existingDeviceToken]);

进行更新。但这确实只是一种解决方法,而不是真正的解决方案。

正如您可能已经收集到的那样,React对我来说仍然是新手,因此我也不是100%知道如何以尽量减少更改价值道具的方式执行此操作,以使提供商不会导致应用重新渲染。

解决方法

我怀疑您在使用enableNotificationsdisableNotifications时在效果上缺少依赖性,但是使用任何一种方法在您的问题中都没有代码。

这是仅当现有DeviceToken更改时才创建函数的代码。

export const SharedNotificationProvider = ({
  children,}) => {
  const [,setState] = useState({
    notificationListenerUnsub: (x) => x,tokenRefreshListenerUnsub: (x) => x,});
  //best to keep this in a ref so you don't create
  //  a needless dependency
  const isEnabled = useRef(false);
  const existingDeviceToken = useSelector(
    (state) => state.firebase.token
  );

  const dispatch = useDispatch();
  const registerToken = useCallback(
    (token) =>
      dispatch({
        type: FirebaseEvents.TOKEN,payload: token,}),[dispatch]
  );
  //all these functions are created on mount and only
  //  change when existingDeviceToken changes
  const registerDeviceToken = useCallback(async () => {
    const deviceToken = await getFirebaseToken();
    if (
      deviceToken &&
      deviceToken !== existingDeviceToken
    ) {
      registerToken(deviceToken);
    }
  },[existingDeviceToken,registerToken]);
  const cleanupNotificationHandlers = useCallback(
    () =>
      setState((state) => {
        state.notificationListenerUnsub();
        state.tokenRefreshListenerUnsub();
        return {
          notificationListenerUnsub: () => {
            /**/
          },tokenRefreshListenerUnsub: () => {
            /**/
          },isEnabled: false,};
      }),[] //no deps,this method never changes after mount
  );

  const disableNotifications = useCallback(
    async (permissionsDeclined) => {
      await removeFirebaseToken();
      registerToken('');
      cleanupNotificationHandlers();
      setState((state) => ({ ...state,isEnabled: false }));
    },[cleanupNotificationHandlers,registerToken]
  );

  const updateNotificationListeners = useCallback(
    async () =>
      // Create listener and store the unsub function (simplified for demo)
      setState((state) => ({
        ...state,notificationListenerUnsub: () => {},tokenRefreshListenerUnsub: () => {},})),[] //no dependencies,function never changes
  );

  const enableNotifications = useCallback(
    async (promptForPermission) => {
      const permissionStatus = await getPushPermission(
        promptForPermission
      );

      if (
        permissionStatus.hasPermission &&
        !isEnabled.current
      ) {
        // Has Push Permissions & Listeners have not yet been setup
        cleanupNotificationHandlers();
        await registerDeviceToken();
        await updateNotificationListeners();
        isEnabled.current = true;
      } else if (
        permissionStatus.hasPermission &&
        isEnabled.current
      ) {
        // Has Push Permissions but Listeners already exist
        await registerDeviceToken();
      } else if (
        permissionStatus.authStatus ===
        messaging.AuthorizationStatus.DENIED
      ) {
        // Push Permissions were declined or removed
        disableNotifications(true);
      }
    },[
      cleanupNotificationHandlers,disableNotifications,registerDeviceToken,updateNotificationListeners,]
  );
  return (
    <SharedNotificationContext.Provider
      value={{
        enableNotifications,}}
    >
      {children}
    </SharedNotificationContext.Provider>
  );
};

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-