Function call is messing up with intersection types

[eliseumds]

Check out line 38 of the following example: https://goo.gl/AdmME5. Does anyone know why it's failing with property 'size'. Property cannot be accessed on any member of intersection type... instead of pointing out first that the second argument passed to mapPropToClass is incorrect?

[dperetti]

Related: #4586

[asolove]

I think the linked issue explains this reasonably well. This is expected though confusing behavior. I’m going to close this issue since it’s not a bug, but am happy to help with adjusting that code to work.

[dperetti]

Returning a misleading, unhelpful error message to the user does sound a bit like a bug, though !

[eliseumds]

I definitely agree with @dperetti.

[asolove-stripe]

This is now improved in Flow 0.55! I had to remove the JSX from the example because Try Flow currently isn't working with JSX. After doing that, the new error message is:

33:     const { size, tracking, ...otherProps } = this.props;
                ^ property `size`. Property cannot be accessed on any member of intersection type
33:     const { size, tracking, ...otherProps } = this.props;
                                                  ^ intersection
Member 1:
26: type ColProps = BoxProps & {
                    ^ BoxPropsError:
33:     const { size, tracking, ...otherProps } = this.props;
                ^ property `size`. Property not found in
26: type ColProps = BoxProps & {
                    ^ object type
Member 2:
26: type ColProps = BoxProps & {                               ^ object typeError:
38: 	mapPropToClass('size', size);
                            ^ number. This type is incompatible with the expected param type of
8: function mapPropToClass(key: string, prop: Object) {
                                              ^ object type

Which helps us reconstruct Flow's reasoning:

• there is no size in BoxProps
• so we instead look in the object type it intersects
• and see a type error in the argument passed to the function.

I think this makes stuff a lot clearer and so this issue is fixed. WDYT, @eliseumds?

[eliseumds]

@asolove-stripe sweet! That's way more useful, thanks =)

[samwgoldman]

38: 	mapPropToClass('size', size);
                            ^ number. This type is incompatible with the expected param type of

This part of the error seems bogus, right? Like the error position is way off.