In the documentation for Editable input:

onChange - Function callback. Use this to call the onChange function of the parent. Returns an object where the key is the label and the value is the new value.

It is not clear what will happen if I don't provide a label. In 2.14 the onChange received the value instead of an object if no label was provided. I just upgraded to 2.17 and this behavior

I've recently upgraded from a much older version of react-toastify which allowed for customizing the default background colors for success/warning/error toasts. There does not seem to be an equivalent option or way to customize these default colors in the latest version. If there is, I could not find it in the documentation.

Is this feature still available or is there another workaround to allo

I like your project a lot. I've been using it for a couple of months now. Just the demo folder never felt natural for me.
Simplify the project by integrating storybook instead of the demo folder.

then users can create documentation of their components.

I think it will benefit all library authors for React/Preact/ vue/ even javascript.

[Storybook](https://git

In v8 we currently support only onDayClick. Other events are very common in date pickers and should be added to the Day component:

• onDayMouseEnter, onDayMouseLeave
• onDayKeyDown, onDayKeyUp, onDayKeyPress
• touch events.

Notes

• These events are already supported in v7.
• Their signature should be the

Starting React Native 0.60.0, fontWeight >=500 are no longer set to bold by default.
fontWeight either needs to be set at 700 or bold for the typeface to be set as bold.

Source - https://github.com/facebook/react-native/blob/3915c0fa6178fbb8aa9b8bd54881cfdbde8fde70/ReactAndroid/src/main/java/com/facebook/react/views/text/ReactBaseTextShadowNode.java#L493

Happy to raise a PR and cha

Is your feature request related to a problem? Please describe.

Move to typescript

Describe the solution you'd like

Move to typescript so we can autogenerate typescript definitions and make maintaining this library much easier

Describe alternatives you've considered

flow? ...ehhh it might be dead

Additional context

As per the documentation in this link, providing user object in unlayer's init method should enable 'User Saved Blocks` feature.

However, when providing user's object via options props like below, it should pass the user's object to init method.

<EmailEditor
 ref={editor => (this.editor = editor)}
 options = { 
     user: {  id: 

1. "react-native run-android" worked perfectly
2. after i install react-native-image-viewer ("npm install react-native-image-viewer --save") i get the following error when execute "react-native run-android": "Configuration with name 'default' not found"

I don't know what could b

I am using a custom prop to force my list to re-render, as recommended in the readme. However, doing so causes me this warning:

Warning: React does not recognize the isScrolling prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `isscrol

Wanted to ask a few questions about features:

• is there in-built tracking?
• native mobile support?
• is there a test runner like karma?
• what audio types are supported?
• are there thumbnail previews?
• mirroring/ over-the-air support?
• i18n?
• VR?
• what's the bundle/library size?

Currently the pagination shows(with text previous and next) even if the page count is zero. Ideally it should get hidden if the page count is zero.

Any thought on adding redux-observable support?

Could look something like:

@kea({
    key: (props) => props.id,

    path: (key) => ['scenes', 'homepage', 'slider', key],

    actions: () => ({
        updateSlide: index => ({ index })
    }),

    reducers: ({ actions, key, props }) => ({
        currentSlide: 

After a refactoring I found that react-sizeme was not working properly anymore; my size.width was 0.

This was my original call (I don't think the HOC version is important): sizeMe()(App)

The issue in the end was the composition of my App component: before the code change the main element was a div, while after that div is wrapped inside the the style-components's `StyleSheetManager

URL in the email is not clickable, it does not appear as a hyperlink , Is there a way to solve this?

It would be great to avoid taking focus when the user right clicks the <ContextMenuTrigger />

I know this is probably impossible to achieve with the longpress action, but it would great if it were the case for right clicks.

We could explore porting use cases tested here to the current setup with react-testing-library.

For things that are impossible to get tested with jsdom we should consider using puppeteer or cypress.