Skip to content

Commit

Permalink
fix(readme): Updated to latest demo.
Browse files Browse the repository at this point in the history
Updated to latest demo.  No actual code fixes, but want NPM to show updated demo link.
  • Loading branch information
ctrlplusb committed Apr 14, 2016
1 parent ae72f83 commit e364e8d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Give your Components the ability to have render logic based on their height/widt

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

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

## Simple Example

Expand Down Expand Up @@ -120,7 +120,7 @@ MyComponent.propTypes = {
})
}

export default SizeMe(/* default config*/)(MyComponent);
export default SizeMe({ monitorHeight: true })(MyComponent);
```

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

## Caveats.

* 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.
* 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.
* 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 comments on commit e364e8d

Please sign in to comment.