change FunctionalComponentOptions to a generic interface

[kaorun343]

so as to specify props and slots()

[HerringtonDarkholme]

Thanks! My concern is typing update is a breaking change for TS users. (I've been bitten by this before).

Should vue's semver also take this into consideration? Ping @ktsn @yyx990803

[ktsn]

hm, as the typings is shipped with core, it should also follow the semver?

[ktsn]

To avoid breaking change, how about rename the generic interface and create a specific interface that compatible current type? like:

export interface RenderContextG<P, S> {
  props: P;
  children: VNode[];
  slots: S;
  data: VNodeData;
  parent: Vue;
}

export interface RenderContext extends RenderContextG<any, any> {}

[ktsn]

Why is this changed to method? In my understand, it should a property of an object.

[kaorun343]

According to a document, it is a function that returns a dictionary.
http://vuejs.org/guide/render-function.html#Functional-Components

[ktsn]

Oh, indeed! I was confused with this.$slots 😆

[kaorun343]

It was a huge breaking change the changes of ComponentOptions that I did. However, compared to ComponentOptions, it will be a smaller impact to change FunctionalComponentOptions and RenderContext, I think...

[ktsn]

I think ComponentOptions update was reasonable breaking change because it was not announced officially about typings and needed revisions for brush up as the stage of pre-release.
However, it is now already released and announced, and it seems many users depends on it.
It may be different problem between code and typings but I think we should be careful about this topic.

[kaorun343]

Then, how about changing only slot: any -> slot(): any?
I'm gonna make pull request again when preparing 2.1...

[ktsn]

It's ok to me.