-
Updated
Jun 8, 2020 - TypeScript
hoc
Here are 285 public repositories matching this topic...
-
Updated
Mar 14, 2020 - JavaScript
current will not bubble up to document when clicking on elements that disappear from the page right after. In this case, _this.__outsideClickHandler(event) will never be triggered.
-
Updated
Apr 4, 2019
Hey,
Thanks a lot for this library!
It appears that you do not copy static methods as described here: https://reactjs.org/docs/higher-order-components.html#static-methods-must-be-copied-over
It seems the convention is that all HOC should do that. The behaviour is somewhat unexpected otherwise.
Are you planning on adding it to the library?
In the meantime, I'm using this workaround:
If I'm not mistaken the blur and black and white effects are related to the placeholderSrc, and opacity creates a blank space then transition to the loaded image.
It would be nice if I define placeholder prop, then the opacity effect could use it
Ex:
<LazyLoadImage src="some-big-image.jpg" placeholder={<div>Loading...</div>} effect="opacity" />
-
Updated
Nov 25, 2018 - JavaScript
-
Updated
Dec 29, 2019 - JavaScript
-
Updated
Nov 28, 2017 - JavaScript
-
Updated
Jun 4, 2020 - JavaScript
react-click-outside's use of findDOMNode triggers a warning when used with React.StrictMode.
https://reactjs.org/docs/strict-mode.html
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of PopoverDetectOutside which is inside StrictMode. Instead, add a ref directly to the element you want to reference.
_("PopoverDetectOutside" is the component wrap
If you have any feedback about how native promises can give users a better debugging experience please let us know :) We're gathering use cases for Node.js to see what we can do better.
-
Updated
Jan 22, 2020 - JavaScript
-
Updated
Aug 30, 2019 - JavaScript
-
Updated
Jun 21, 2019 - JavaScript
-
Updated
Aug 10, 2019 - JavaScript
-
Updated
Jul 1, 2020 - TypeScript
-
Updated
Jul 4, 2020 - TypeScript
-
Updated
May 7, 2019 - JavaScript
SSR Support
Problem:
I get a 'window is not defined' error when I try to use in SSR application with razzle framework because virtualDebugger is using 'window' object without checking it is exist or not.
Even I got an error without using virtual debugger.
Solution:
Adding basic 'window' check for SSR support.
-
Updated
Jul 6, 2019 - JavaScript
Improve README
Add more information and examples:
- Add a working example with React Router
- Add an example with LoadingComponent
- Add an example with shared authentication layer
- Add an example with shared style
- Add an example with more complex
props
-
Updated
Jul 16, 2017 - JavaScript
-
Updated
Aug 30, 2017 - JavaScript
-
Updated
Sep 23, 2017 - JavaScript
-
Updated
May 31, 2020 - JavaScript
Improve this page
Add a description, image, and links to the hoc topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the hoc topic, visit your repo's landing page and select "manage topics."
I'm trying to migrate from v1 to v2 of redux-auth-wrapper. I'm sticking with RR3 for the moment since I'm using SSR and it will be a larger undertaking to migrate everything to RR4 (though I do want to migrate eventually).
That being said, I'm running into some issues with getting everything working like it was under v1. To summarize, I'm not sure how to get a FailureComponent working under v