sgny

`style` prop in React Native components take a single `Style.t` object or an array (or list) of them. Until now, we used to cast `array(Style.t)` as `Style.t`, but we have...

I suppose we could use a method to convert a `value(calculated)` to `value(regular)` but perhaps we don't really need to differentiate between those types in the first place. I had...

> If you plug `regular` in functions that expect `calculated` (and vice versa) you’ll get runtime errors (unless something changed in more recent RN versions) Do you have any concrete...

> @sgny you'd have to try. My memory might be failing me but I think those type definitions are correct. @wokalski I've been trying and it appears that the disctinction...

> As we know, all stylesheet values cannot be used in various places to add/combine styles (because they are `int`). Also we cannot use array() in stylesheets (runtime error). >...

> You are right. It seems `absoluteFill` has changed. They are the same now. Sooo not sure we need `absoluteFillObject` has this thing is documented as being a thing you...

I'm copying my comment as the PR is already merged. What if instead of `withOptions` we used `withOptional` (or `withOptionals`)? Then we could have optional parameters or configs without causing...

Not that they are too similar, but most arguments are in the end options in a config. Most are required and rarely when we have optional arguments it might be...

`ReasonReact` is the old API. Since it's pretty easy to migrate from that to the new API, I don't think it's relevant any longer. I think the documentation is fairly...

I had chosen this setup to prevent breaking and I find it more straightforward to avoid multiple functions (at the risk of the user passing multiple props rendering to the...