Jacob Parker

Thanks for this write-up! It's really comprehensive, and I definitely learned a lot from reading it

This isn’t quite right. If you put a border radius of 100% on a rectangle in CSS, you’ll get an ellipse. If you do it here, you’ll get a pill...

I don’t think this is the right fix. Why aren’t there insets?

We can't merge this change because it'll cause excessive renders. If you figure out why the insets aren't getting set, we can look at merging something that fixes that issue

I think that PR looks useful - but won't change things in the monorepo I linked: (by chance) every package that uses a pinned dependency includes all the child pinned...

Added behind an option. Can confirm this worked when using in combination with the plugin you suggested! https://github.com/davidtheclark/postcss-simple-extend/pull/12

How does this work with `useImperativeHandle`? There were probably cases where you might have conditionally returned `null` for this cleanup style thing ```js forwardRef((props, passedRef) => { const [isEditing, setIsEditing]...

There’s definitely some configuration that we’re missing the documentation for here. If you fancy taking a stab at documenting, PRs are happily accepted

Does it happen with just this library - or is it only with react navigation?

For the lag, try setting `contentInset` and `scrollIndicatorInsets ` rather than padding - you'll be able to skip a layout update. You could also put a `SafeAreaView` with the insets...