The io-flow-types from orlandoc01

io-flow-types's People

Contributors

Stargazers

Watchers

io-flow-types's Issues

typed-contracts reference

Great to see that someone still planning to do this thing for Flow.

It worth check gcanti/babel-plugin-tcomb#178.

typed-contracts seems to be built around a similar idea, so maybe something useful can be learned from it.

Union type with undefined

Hello,
I'm getting an error on this:

t.exact({
  required: {
    myField: t.union([t.Object, t.Undefined]),
   ...
  },

I'd like to be sure on this type:

type MyType = {
  myField: ?Object,
  ...
}

Or construction I'm using is not correct?

Flowtype errors

At least the latest Flowtype 0.110.1 gives me several errors like that:

Error ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ node_modules/io-flow-types/lib/types/props/exact.js.flow:8:37

Cannot determine a type for object type [1]. object type [2] cannot be spread because the indexer string [3] may
overwrite properties with explicit keys in a way that Flow cannot track. Can you spread object type [2] first or remove
the indexer?

        node_modules/io-flow-types/lib/types/props/exact.js.flow
         5│ import type { MixedFlowType, Is, Validate, Context, Encode } from '../index.js';
         6│
         7│ type ExactObj<Required: Props, Optional: Props> = $Rest<
 [1][2]  8│   {| ...$Exact<Required>, ...$Exact<Optional> |},
         9│   $Rest<Optional, {}>
        10│ >;
        11│

        node_modules/io-flow-types/lib/types/props/base.js.flow
    [3] 30│ export type Props = $ReadOnly<{ [key: string]: MixedFlowType }>;

Any workaround, please?

Recommend Projects