the `components` option in createComponent() doesn't support vue2 options about composition-api HOT 24 CLOSED

Casting as any will break all the types support.
One of the workarounds right now is to take all the keys, except props an setup outside the createComponent function.

export default {
  components: {
  },
  ...createComponent({
    setup(props) {
    },
    props: {
    }
  })
}

from composition-api.

This is already been fixed in dev branch.
https://github.com/vuejs/vue-function-api/blob/703bf300308ff3a550b236cd3de461fcec9f2213/src/component/component.ts#L70-L73

from composition-api.

createComponent only support using with an inline render function return by setup now.

Why so? By spec, its not written anywhere that setup() and other properties cannot be used together (especially component and name for which I don't see a clear alternative).
There even is an example of mixed-usage where setup() and data are used together.

from composition-api.

the name option in createComponent() how to dealwith?
Is there any other way besides setting any type?

export default createComponent({
   name: 'componentName'
})

@liximomo

from composition-api.

You are welcome to work on solving this challebge.

from composition-api.

I'm confused. Is the final behavior going to no longer allow name and components properties within the createComponent function? This is important to know so that I can either downgrade the package for the time being or begin migrating to a newer standard.

from composition-api.

@liximomo Seems that on @vue/composition-api 0.1., components work BUT not for lazy ones :

Classic import

Lazy loading

from composition-api.

createComponent only support using with an inline render function return by setup now.

import {createComponent, createElement as h } from 'vue-function-api';
import HelloWorld from './components/HelloWorld.vue';

export default createComponent({
  setup() {
     return () => h(HelloWorld)
 }
});

You can make it work by a force-cast as well.

import {createComponent, createElement as h } from 'vue-function-api';
import HelloWorld from './components/HelloWorld.vue';

export default createComponent({
 components: {HelloWorld}
} as any);

from composition-api.

OK, thank you. I have another question, could I use it along with template? Using render function will override the template.
And I changed the issue's title to avoid misleading.

from composition-api.

@HermitSun Yes. You can use it with the template, but it still requests a force-cast for passing components options.

from composition-api.

I got your point. Thanks a lot.

from composition-api.

This change is too big, I plan to downgrade the version。
Every time I upgrade to a new version, I have to change the code again.

from composition-api.

I think you should not cast the options obect to any when you do provide a setup function. Then TS can correctly infer types for setup() arguments.

from composition-api.

Maybe we can expand the interface? Just like @PatrykWalach said in issue#63:

import {ComponentOptions} from 'vue-function-api/dist/ts-api/component';
import {AsyncComponent, Component} from 'vue';

declare module 'vue-function-api/dist/ts-api/component' {
    interface ComponentOptions {
        components?: {
            [key: string]: Component<any, any, any, any> | AsyncComponent<any, any, any, any> 
        };
    }
}

from composition-api.

Before trying tackle the problem, I need to understand it in its entirety.
components and name are probably not the only properties which are needed but have been removed from the type, can you provide me some context about this change? Why was it necessary? Why implementing it required dropping those properties and/or not being a Vue instance anymore (if it was such before)? Are the two things related?

from composition-api.

The properties probably has been removed unintentionally, the options inside createComponent should extend the default vue ComponentOptions. You can see inside /ts-api/component that VueProxy which is result of the function extends ComponentOptions, which means it should return a proper Vue instance. I'm not too familiar with the types inside Vue so I couldn't find a solution, but I think problem is located inside this file.

from composition-api.

Casting as any will break all the types support.
One of the workarounds right now is to take all the keys, except props an setup outside the createComponent function.

export default {
  components: {
  },
  ...createComponent({
    setup(props) {
    },
    props: {
    }
  })
}

I thought this is a better solution. Yet I still wanna see types contain components option originally.

So why are you removing it actually?

from composition-api.

@jorgy343 It will allow all vue2 options.

from composition-api.

While the issue is not fixed, I believe that best way to work it around is by temporarily replacing export default createComponent({ }) by export default { }. This will break Typescript inference but it will not break compilation. If using props, you might also need to go with setup(props: any) {}.

It should be fairly quick to rollback to using createComponent once the issue is fixed.

from composition-api.

@kevinmarrec I couldn't reproduce it. Can you provide an online example?

from composition-api.

This is already been fixed in dev branch.
https://github.com/vuejs/vue-function-api/blob/703bf300308ff3a550b236cd3de461fcec9f2213/src/component/component.ts#L70-L73

Can you release a version as soon as possible? 2.2.1 for vue-function-api

from composition-api.

@bigmeow The package has been rename to @vue/composition-api.

from composition-api.

This already got fixed in the new package @vue/composition-api.

from composition-api.

@liximomo About #62 (comment), I opened #81 with reproduction

from composition-api.