Currently, setStateAction is used in Effect to update state, which is actually the responsibility of Reducer. Effect should only perform side-effects and dispatch actions. So please remove this API.

React native is compatible with hooks.

The devDependency @types/lodash was updated from 4.14.126 to 4.14.127.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @typescript-eslint/eslint-plugin was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

solution A: using decorators to distinguish singleton or non-singleton

@Singleton()
class SomeThing extends Ayanami {}

@Transient()
class AnotherThing extends Ayanami {}

solution B: export another class for non-singleton usage

class SomeThing extends NonSingletonAyanami {}

现在ayanami的类不支持使用getter，能否通过computed装饰器增加对getter的支持？
使用起来类似这样：
@computed get totalPrice() { const good = goodList[this.index] return good.number * good.price; }

something like Ayanami.connect(SomeComponent)

The devDependency @typescript-eslint/parser was updated from 2.3.0 to 2.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

https://github.com/zalmoxisus/redux-devtools-extension/blob/master/docs/API/Methods.md

• log actions 905f5e8
• able to disable it
• time travel
• trace actions calls
• log actions should not affect main thread ⚠️

• [问题描述]
  ayanami constructor里面注入value会导致依赖报错

• [复现步骤]

1. useAyanami时指定scope
2. 在Injectable provide一个value，通过@Inject注入ayanami对象

• [版本]
  [email protected]之后的版本都能复现

• [codesandbox]
  https://codesandbox.io/s/ayanamiminimal-example-u1cto

• [问题源码]
  

  ayanami/src/core/scope/utils.ts

  Line 40 in c601a84

  const newInstance = new constructor(...deps)

  
  没有对Inject value的情况做处理

Using immer in complicated state is much more concise than POJ.
For example:

interface State: {
  ui: {
    comments: { [index: string]: Array<Comment> }
  }
}

@ImmerReducer()
addComment(state: State, { payload }: Action<{ articleId: string, comment: Comment }>) {
  state.ui.comments[payload.articleId].push(payload.comment)
}

vs

@Reducer()
addComment(state: State, { payload }: Action<{ articleId: string, comment: Comment }>) {
  const comments = state.ui.comments.get(payload.article)
  return { ...state, ui: { ...state.ui, comments: { ...state.ui.comments, [payload.articleId]: [...comments, payload.comment] } } }
}

The devDependency @typescript-eslint/eslint-plugin was updated from 1.11.0 to 1.12.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

if we invoke else service method suck as this.getActions() inside the effectActions[actionName] function in sync way, it will cause an error:

InternalError: "too much recursion"

the effect can be:

  @Effect()
  fetchInfo(url$: Observable<string>):Observable<EffectAction> {
    return url$.pipe(
      switchMap(url => from(client.get(url))),
      mergeMap(data => of(this.getActions().setData(data), this.getActions().setLoading(false))),
      startWith(this.getActions().setLoading(true)),
    )
  }

the effect init function is :

because the startWith is sync, so this.getActions() will request the ikari instance, but the ikari instance is not fully constructed at that time. so it will invoke the create function again and agian...

The devDependency @types/react was updated from 16.8.13 to 16.8.14.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I tried to use ayanami in RN but failed. Can ayanami support rn or is there any plan to adapt rn...

Since Ayanami is a singleton, the state and effect actions are shared for each test instance which is a bad practice for testing.

现在有比较多的场景都需要effects执行完毕的回调，比如loading,编辑弹窗完成后异步提交结束后关闭弹窗，但是现在的异步actions执行的结果的undefined,无法获取执行完毕的回调，需要通过设置额外的state来标示，然后通过判断state的变化来执行对应的操作，每个类都需要写一遍，感觉有点复杂

The devDependency @types/react was updated from 16.8.16 to 16.8.17.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

When I trying to update state in render just like using getDerivedStateFromProps, the initial Ayanami state cannot be ignored. This might not be a problem, but the behavior is different with just storing state in component.

The example:
state in ayanami: https://codesandbox.io/s/ayanamiminimal-example-zw3fi?fontsize=14
state in component: https://codesandbox.io/s/test-getderivedstatefromprops-lricw?fontsize=14

RxJS is great as process management, but sometimes our Effect dosen't need too much async management ability. So I really want a simpler way to provide async management ability.

@GeneratorEffect()
async fetchUserInfo(payload:  T) {
  const response = await client.query({ ... })
  try {
    yield this.getActions().setUserInfo(assertSuccess(response))
  } catch (e) {
    yield this.getActions().getUserInfoFailed(e)
  }
}

The devDependency @types/lodash was updated from 4.14.129 to 4.14.130.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @typescript-eslint/parser was updated from 2.6.0 to 2.6.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/react was updated from 16.8.10 to 16.8.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

目前项目中classComponent比较多，用不了useAyanami hooks，connect方法能提供第三个参数支持scope，跟useAyanami方法保持一致么？

Current we have to test action in a React way, for example:

testRenderer.root.findByProps({ id: action }).props.onClick()

which is no efficient. We need a better way to test.

如题，是不是应该改成loadsh.get或者lodash/get?

First, we should align behavior with redux reducer, or we need change the name Reducer to something else.

The second, in most case, action & payload is optional, there are too many codes in Modules like :

setLoading(_: void, state: State)

too ugly.

新版本里useAyanami不支持传入scope了，是基于什么考虑去掉了这个特性呢？后续有没有替代方案支持组件间的数据隔离

• make sure errors won't affect the main state$
• more friendly error info

The devDependency @types/lodash was updated from 4.14.135 to 4.14.136.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I want to store some state (for example i18n info) into ayanami modules so that I can get feedback immediately I change the language;
However, I also need to use current i18n info to do sth for example toast some messages. But I am not sure is there a way to access the info stored in the ayanami modules outside React Components just like a getStores function in redux?

The devDependency @types/express was updated from 4.17.1 to 4.17.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/express is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @typescript-eslint/eslint-plugin was updated from 1.9.0 to 1.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

use means hooks already. useHooks looks too verbose.