❌ to the ☕ script! ES6 is cleaner, more modern, and has a much more reliable linter—plus, people know how to read it—so we want to convert everything in the codebase. Most of the code is already there, but there are still specs written in Coffee.

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

Problem

Here are the types for a ts test https://github.com/paularmstrong/normalizr/blob/master/typescript-tests/entity.ts#L11

Since in the normalized entities all relationships are all id type this should be string instead of User

{
  ...
  user: string
}

ReactNativeNWReactCalculator@1.0.0 start /Users/zjh-mac/Documents/react/react-native-nw-react-calculator-master
node node_modules/react-native/local-cli/cli.js start

┌────────────────────────────────────────────────────────────────────────────┐
│ Running packager on port 8081. │
│

嗨, 您好
在學習CH05的時候,遇到一個問題
發現在 webpack.config.js 裡面的 module: { preLoaders: [ { ... } ],
似乎造成webpack錯誤 無法執行

如下terminal截圖

稍微查了一下,解決方法是用 webpack@2.1.0-beta.22 版本
我目前是 "webpack": "^2.2.0", _應該也

Motivation

Some IDEs like IntelliJ don't display the javadoc custom tags at all in their javadoc popup.

As a consequence, discovering information about the discard and continue support might be difficult.

Searching the HTML version or the source to look for information about support might still be acceptable, but the tags should not be the only places where eg. a caveat or structuring im

A lot of what Flux can do is not explicitly written down. Regularisation is a good example; just grabbing your parameters and summing them is really simple and intuitive, but if you're used to frameworks that provide an explicit API for this, you might get not think of it, or assume it's not supported at all if it isn't in the docs.

So we need to document Flux "design patterns" that explicitly

React 16.3 introduce getDerivedStateFromProps. currently we are using in connectToStores.js and createNavLinkComponent.js.

React already starts throwing warning if client migrate the component to use getDerivedStateFromProps while wrapping with connectToStores

![screen shot 2018-04-25 at 6 14 47 am](https://user-images.githubusercontent.com/3906130/39248072-fee78990-484f-11e8-8689

I think it would be handy if Undux used React.forwardRef() to make sure that any refs attached to components created using withStore got attached to the wrapped component instead of the wrapper itself. Thoughts?

Hi I passed the example code to react native and works wonderful but redux-devtools doesn't work.

On the documentation you said During development redux-devtools are automatically enabled. Install the extension. what's mean automatically enabled? maybe I missed something...

Here is my code:

store.js

import createStore from 'react-waterfall'

const config = {
  initialState: {

Hi,

I just read your great article http://arqex.com/991/json-editor-react-immutable-data

I'd like to suggest you to make your didactic materials interactive: docs/README/blog posts.

For that purpose, you could use the KLIPSE plugin like one guy did for immutable.js in this [interactive article](http://untangled.io/immutable-js-an-introduction-with-exam

Please check the reproducible example here: https://github.com/michaelr524/reactor-netty-ssl-leak

mvn clean package
java -jar target/reactor-netty-ssl-leak-1.0-SNAPSHOT.jar 

• Reactor version(s) used: 0.9.4.RELEASE
• Other relevant libraries versions (eg. netty, ...):
• JVM version (javar -version):
  openjdk version "12.0.2" 2019-07-16
  OpenJDK Runtime Environment (build 12.0

Hi shiningjason,
感謝你的教學, 很清楚明瞭,
我在學習過程中發現一點問題, 回報一下希望能幫助到你更版

“Level 7. 培養好習慣，設計防呆的 React 元件”章節有用到React.PropTypes.string
但React v15.5後已經不支援React.PropTypes, 進行到這段會報錯
(教學中提供的react cdn連結 https://cdnjs.com/libraries/react 目前已經是v16)

// 1. 使用 propTypes 定義參數的型別
TodoHeader.propTypes = {
  title: React.PropTypes.string,      //Error: Cannot read property 'string' of undefined
  username: 

Was getting a getState() is not a function error when trying to use the async() way of dispatching an async action, and after hunting through the issues I discovered that lexich/redux-api@02eddbf made all the dispatches return promises (awesome!! ^_^). It was hard to track down; would be awesome if the docs mentioned this somewhere.

What kind of issue is this? (check at least one)

• Report a bug
• Feature Request
• Question
• Discussion
• Documentation
• Other, please describe:

What version of Microcosm is this for

All

Additional Comments (optional)

We should dedicate a section of the README to cover microcosm-devtools integration and usage. These tools might not yet b

https://github.com/defunctzombie/zuul is unmaintainced.
We want to replace zuul to another testing library.

We need a script to create a folder in /packages for a new package with already predefined dot files, build and test scripts and etc

According to the project README, all contributions should include a README. It would be very helpful for new users (including me) if this applied to all models, but none of the models that I have looked at have one. This includes

cppn dcgan_mnist mnist