autoResize option enabled

[ZachHaber]

Fixes #7

It's not the prettiest way of doing this (a lot of flashes), but I have another branch I set up with a bunch of changes to enable an external resize-observer approach.

I set autoResize: true by default as having it not resize would be a breaking change, unfortunately.

For reference, here's the changes I set up to do the resize-observer approach, and if you decide we should go that route, I'll redo that branch with only the changes needed, and better commit messages. Note, there was a need to surface both the networkRef and the div's ref for this.
https://github.com/Wokstym/react-vis-graph-wrapper/compare/resize-observer

[Wokstym]

I'm much bigger fan of approach shown on resize-observer branch - purely based on looks.

Could you explain what is the purpose of innerRef seen in ResponsiveVisGraph? Also remember to change example in readme if we go that way

[ZachHaber]

I'm much bigger fan of approach shown on resize-observer branch - purely based on looks.

That's entirely fair, it definitely looks nicer, but is more complex to set up. The main part is that we can just indicate that there is a responsive option in the base library, even if it looks bad. It'll be more performant on worse computers since they are debouncing the change events significantly.

Could you explain what is the purpose of innerRef seen in ResponsiveVisGraph? Also remember to change example in readme if we go that way

innerRef is needed because you can't always guarantee that there will be a ref passed in from the parent (or what the shape of it is i.e. function vs RefObject). Ideally, we'd need to also support forward ref for the div as well in case the user wants that for things like focus handling.

The other option due to how basic the ResponsiveVisGraph is, is to export the hook, and put a write-up of the code to run that hook on storybook mdx file and the main readme.

[WikKam]

Same opinion as Grzesiek, the one with resizeObserver just looks so much better. Maybe we should keep both of them and give user the choice?

[ZachHaber]

Yup, we can definitely make both available. The one that this PR is displaying is just built into the component, so we just need to indicate to users how to turn it on.
With that I'll close this PR and get a new one with the other set of changes up shortly.