Brandon Dail

Can you provide an example reproducing your issue? Unfortunately, isn't enough information here for me to provide any meaningful help.

@binoy14 go for it! Feel free to ping me here with any questions

@binoy14 I would probably mock `window.addEventListener` and `window.removeEventListener` and then assert that they've been called at the correct point and the correct number of times See Jest's doc page on...

I'd love to add support for this! Maybe we could make it opt-in at first?

@CodinCat great idea! There's already a small demo application in the repo, we can probably just get it published to Github Pages?

Thanks for the issue @JulienPradet! You bring up a great point, current `react-perimeter` has no way of knowing if an element is moved outside a `resize` event. I think the...

I'm really hesitant to implement a solution that involves constantly redrawing the boundaries (even if it's debounced). Ideally, there would be a way for the application to tell `Perimeter` that...

I think this is very related to https://github.com/aweary/react-perimeter/issues/21 I'd like to support this in a really flexible way. I'm thinking we can add a prop that takes a function that's...

Hey @dtinth! > It would be much easier for us to debug if, when the nested update count exceeds 1,000 (current NESTED_UPDATE_LIMIT), we could see what components are involved in...

> I don't think we would want to add any DEV-only behavior into the profiling build (other than profile times) because the purpose of that build is to be almost...