Type inference and conflicts #15

Closed
kitsonk opened this Issue Nov 19, 2015 · 1 comment

Projects

None yet

1 participant

@kitsonk
Member
kitsonk commented Nov 19, 2015

I don't know if we have worked through all the edge cases with type inference and conflicts... I can't remember what happens at the typescript level with something like this:

const fooFactory = compose({
    foo: 'bar'
});

const fooBarFactory = compose.extend({
    foo: function () {
        console.log('bar');
    }
});

const fooBar = fooBarFactory();

What type is fooBar.foo. From a code perspective, it is last one wins, but what happens with the type? Do we need to do something about that?

@kitsonk kitsonk added the discussion label Nov 19, 2015
@kitsonk kitsonk added this to the alpha.2 milestone Mar 11, 2016
@kitsonk kitsonk modified the milestone: 2016.04, alpha.2 Apr 8, 2016
@kitsonk
Member
kitsonk commented Apr 8, 2016

@maier49 and I have discussed. There is currently no good way of handling conflicts other than educating the end-user on how it works at the moment.

@kitsonk kitsonk closed this Apr 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment