Undocumented breaking change in 0.9.2

[kassens]

12b2137 introduced a breaking change where non-nullable fields are no longer considered leaf types by isLeafType.

See the breakage reported in facebook/relay#1614.

[leebyron]

This one's ambiguous, but I agree should have been included on the changelog. It was a bug fix, but that did result in behavior change

[kassens]

Feel free to close if the change log is immutable.

[wincent]

It's not immutable.

[wincent]

Note that it was already in the changelog as:

• Improvements to Flow checking (RFC: More flow-friendly thenable checking. #699) and type safety (Fix: Type safety for TypeInfo. #698), (Fix: isLeafType matches type definition. #697).

but at the time I wrote it I didn't realize it was a breaking change. I've edited the release notes to instead say:

• Remove ambiguity in isLeafType check: it no longer performs named type unwrapping and is consistent with the other isCompositeType/isAbstractType checks (Fix: isLeafType matches type definition. #697).

Feel free to edit them further if you think they can be improved.

[kassens]

This is perfect. Flow checking/type safety sounded internal or that they wouldn't affect runtime.