We shouldn’t be missing that case. We even have a test for it 😣. See: https://github.com/facebook/flow/blob/master/packages/flow-upgrade/src/upgrades/0.53.0/ReactComponentExplicitTypeArgs/__tests__/fixtures/ComponentNamedImport.js
Did you add
// @flow to the top of your file?
Flow has better support for React. TypeScript does not support default props, does not support strictly typed children, and does not provide useful utility types like Flow does.
If a library is written in Flow then the Flow version and the package version are tied together. However, you could create a libdef for your package for an older version of Flow and upload it to
flow-typed if you want to still support older versions of Flow 😊
You don’t need
clientMutationId with Apollo Client, so you can just leave it out entirely.
clientMutationId is merely an implementation detail for Relay 1 and so it should be nullable in your schema so clients are not required to use it.
Yep the dev must do this when using
client.writeFragment directly, but the proxy object provided in
update will automatically rollback any change to the store for you, so don’t be afraid to do crazy updates 😊