Skip to content

Commit e364e8d

Browse files
committed
fix(readme): Updated to latest demo.
Updated to latest demo. No actual code fixes, but want NPM to show updated demo link.
1 parent ae72f83 commit e364e8d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Give your Components the ability to have render logic based on their height/widt
2323

2424
Perhaps it's easiest just to show a live example:
2525

26-
https://react-sizeme-example-armpgxfodd.now.sh
26+
https://react-sizeme-example-xcnwvtdzmb.now.sh
2727

2828
## Simple Example
2929

@@ -120,7 +120,7 @@ MyComponent.propTypes = {
120120
})
121121
}
122122

123-
export default SizeMe(/* default config*/)(MyComponent);
123+
export default SizeMe({ monitorHeight: true })(MyComponent);
124124
```
125125

126126
## On the First Render of your Component
@@ -187,5 +187,5 @@ We make use of the awesome [element-resize-detector](https://github.com/wnr/elem
187187

188188
## Caveats.
189189

190-
* Server Side Rendering is not supported. I am still thinking of the best approach on what to do in the case of a SSR request. Perhaps I will allow you to pass in a default `size` configuration that should be resolved should the component run within an SSR environment. I'm open to recommendations on this one.
190+
* Server Side Rendering is not supported. I am still thinking of the best approach on what to do in the case of a SSR request. Perhaps I will just return null values for width/height. Undecided. Any recommendations are welcome.
191191
* Whilst execution is performant and we try and do smart rendering mechanisms we don't recommend that you place a crazy amount of size aware components into your render tree. If you do require this I highly recommend you do some decent browser testing for impact.

0 commit comments

Comments
 (0)