flux

Should you ever use this.setState() when using redux? Or should you always be dispatching actions and relying on props? Clear uses of setState would be for UI components that have local display state, but aren't relevant for the global application. For example a boolean that represents whether a specific dropdown menu is actively displayed doesn't need to be in global state, so it's more conveniently controlled by the menu component's state. Other examples might include the collapse/expand state of lines in an accordion display of a hierarchy. Or possibly the currently selected tab in tab

语法 首先 React Native 所使用的语法是 JavaScript。 首推书籍是 JavaScript 高级程序设计（第3版）购书地址： http://item.jd.com/10951037.html 把本书的前 7 章看完，就能很好的了解 JS 的基础语法。不用看 BOM DOM 之后的章节，这块是针对游览器的。 React Native V0.18 之前采用的是 JavaScript 的 ECMAScript5 的标准，之后采用的是 ECMAScript6 (ES2016) 的标准，进行编程。 这部分要学习的是 ECMA2016 http://es6.ruanyifeng.com/ 主要的是 let和const命令 变量的结构赋值 Iterator和for..of循环 Class Module 这几章。 框架 以上是语法部分，接着我们知道，React Native 是基于 React 框架的搭建而成的。 通过官网学习 React 就好 https://facebook.github.io/react/index.h... 以上是基础部分，接着轮到我们的主角登场 React Native 官网就好，现在接口更新快，中文的文档难免不全。 React Native 官网 https://facebook.github.io/react-native/ 中文 http:/

I'm using alt as my flux implementation for a project and am having trouble wrapping my head around the best way to handle loading stores for two related entities. I'm using sources feature along with registerAsync for to handle my async/api calls and bind them to my views using AltContainer. I have two entities related one to one by the conversationId. Both are loaded via an api call: Once my job store is loaded with data I want to fill a conversation store. I use a source to load the job store: module.exports = { fetchJobs() { return { remote() { return axios.get('api/platform/jobs'); },....

I have been using Vuex for awhile now, and I have always been following the pattern: Components use Actions to commit Mutations to mutate the Store. I thought this was the proper way to do things considering this diagram from the docs: I came across code where people were committing mutations directly in components, and not even creating simple actions which have no purpose other than to trigger mutations. I even found several examples of this in the Vuex docs. I figured since it's used in the docs this must be an acceptable pattern, and I was wondering if skipping Actions and directly

资源整理。 1 Coding: 1.卫星影像深度学习资源。 satellite image deep learning 2.runoff tools为MOM生成径流文件的一些工具变得轻而易举。 runoff tools 3.NOAA-GFDL海冰模拟器V2.0。 SIS2 4.该仓库提供涉及MOM6和SIS2的模型的配置（输入参数和数据）及其相应的回归数据（用于测试）。 MOM6 examples 5.MOM6源码。 MOM6 6.FMS是一个软件框架，用于支持大气，海洋和气候系统模型的有效开发，构建，执行和科学解释。 FMS 7.各种学习笔记，如VIM，一些书的。 notes 8.一系列R脚本，用于预处理WRFChem（WRF-Chem）空气质量模型的输出。按照需要的方式重新格网化数据。 WRF Chem 9.使用Python的图像多边形注释（多边形，矩形，圆形，线形，点和图像级标记注释）。 labelme 10.R语言包GLMMadaptive的幻灯。 GLMMadaptive presentations 11.R语言包gt的一些小例子。 gt awesome tables 12.R语言包textdata，目标是构建一个文本相关数据集的存储库，以便于访问。 textdata 13.“Advances in Archaeological Practice'”论文的研究纲要。

I've been searching for a while about React's hooks now, and one question became persistent in my head. Will hooks overthrown redux? This is a fairly old discussion so first a little bit of context : State Management with React Hooks — No Redux or Context API What do Hooks mean for popular APIs like Redux connect() and React Router? redux-react-hook A lot of people (React's team included) seens to think that redux and similars will just going to adapt to the new API, turning the HOC's approach obsolete, but my question is: With custom hooks, use reducer , and a well thought logic why do I need