-
Hi Guys, I like your library a lot but the only problem is the appearance of a warning concerning the version of React. Indeed, if we want to switch to React 17, unfortunately the Reader component wil…
-
Hi I'm getting this warning
`Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.
* Move data fetch…
-
Hello @felippenardi
after using this library with React 17, I've got the warning:
> componentWillUpdate has been renamed, and is not recommended for use
```
* Move data fetching code or sid…
-
### Description
This has been requested by several users over the time.
### Implementation ideas
_No response_
-
Please, update package to eliminate debug warning message:
```
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycl…
-
``
results in
```
}
react-dom.development.js:12430 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles fo…
-
https://developer.android.com/topic/libraries/architecture/index.html
- ViewModel
- LiveData
- Lifecycles/LifecycleObserver/LifecycleOwner etc
- Room
-
Support the same options that `logstash` does for managing index lifecycles: https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/docs/index.asciidoc#index-lifecycle-managemen…
-
```
Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMoun…
-
```
Warning: componentWillMount has been renamed, and is not recommended for use. See
* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename compo…