Things to consider:

• Specific error type (list of strings?)
• Errors in arrays
• Errors for compound values (arrays and object)

With current boolean implementation, default value is false. It'd be nice to control this.

We may use realue awesome HOCs on top of third parties components which have different various onChange signatures.

The simplest case i can think is onChange(value). For instance, this is the case for react-datetime or react-bootstrap-typeahead. In that case, we add the same hoc:

const withRealueOnChange = withHandlers({
  onChange: ({ onChange, name }) => value => onChange(value, name),
})

Several ideas:

• Move onChange signature to onChange(value, payload).
• property and item hoc provide on additional props onChangeSimple
• Handle the case where name is undefined and use by the default the one from props

What do you think?

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Changes

• All hocs will be converted to hooks

Following modules will be exported into their own package:

• queries
• immutables

• { value } as the main resource to render
• { name, onChange } to enable upwards communication
• Derive behavior from props, not from decorator parameters
• { onPush } to bypass filters
• { onPull } to retrieve value from parent
• More general:
  • { [on${action}] } for upwards communication

const MyComp = compose(
   withBounds(),
   logProps(["width"])
)

Displays width fairly fast if expanding the window, displays almost pixel per pixel if we shrink the window

The devDependency parcel-bundler was updated from 1.10.2 to 1.10.3.

🚨 View failing branch.

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

parcel-bundler 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 prettier was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

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

prettier 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 🌴

Version 0.19.3 of @std/esm was just published.

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

@std/esm 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 🌴

There have been updates to the react monorepo:

• • The dependency react was updated from 16.6.1 to 16.6.2.

• The dependency react-dom was updated from 16.6.1 to 16.6.2.
• The devDependency react-test-renderer was updated from 16.6.1 to 16.6.2.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Decorator definitions should include examples to better illustrate their features and purpose.

The devDependency eslint was updated from 5.15.3 to 5.16.0.

🚨 View failing branch.

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

eslint 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 prettier was updated from 1.18.0 to 1.18.1.

🚨 View failing branch.

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

prettier 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 🌴

given
withChildren(MyComp),
crashes with

Uncaught (in promise) TypeError: item is not a function
at children.js:19
at children.js:49
at arrayMap (lodash.js:753)
at map (lodash.js:10198)
at children.js:48
at withChildren.render (children.js:51)
at finishClassComponent (react-dom.development.js:15319)
at updateClassComponent (react-dom.development.js:15274)
at beginWork (react-dom.development.js:16262)
at performUnitOfWork (react-dom.development.js:20279)
at workLoop (react-dom.development.js:20320)
at renderRoot (react-dom.development.js:20400)
at performWorkOnRoot (react-dom.development.js:21357)
at performWork (react-dom.development.js:21267)
at performSyncWork (react-dom.development.js:21241)
at requestWork (react-dom.development.js:21096)
at scheduleWork (react-dom.development.js:20909)
at Object.enqueueSetState (react-dom.development.js:11595)
at promisedProp.push../node_modules/react/cjs/react.development.js.Component.setState (react.development.js:336)
at promises.js:130

a simple
withChildren(MyComponent, () => (props) => props),
does the trick for now.

There have been updates to the react monorepo:

• • The dependency react was updated from 16.8.0 to 16.8.1.

• The devDependency react-dom was updated from 16.8.0 to 16.8.1.
• The devDependency react-test-renderer was updated from 16.8.0 to 16.8.1.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴