Fixed ResponsiveContainer ref#2784
Conversation
|
This would be a breaking change though, so I guess it would have to wait for a major version. |
|
Added some labels, most likely fine to add this as a breaking change in 3 if we ever get there |
|
Not this change is breaking. But this bug is a breaking issue. |
|
Not sure what you mean. Those that use those functionality have this referenced a certain way. If we change it in a minor or patch release it will break them. |
|
@ckifer |
|
Yeah but it's a breaking change, so not until 3.x. Which is still timeframe TBD as we gather other breaking changes |
|
I understand. |
|
Going to close this PR in favor of re-opening the issue #3718. Harder to keep a PR up to date while waiting for a major version |
Until now, if user wanted to access a ref object, they had to use
ref.current.current.This was unfriendly and not clear, so I fixed it.