0.12 Plan - feedback welcome

[yyx990803]

Hi Vue.js users, here is a list of changes I'm planning for the 0.12 release. The goal is to remove some cruft in the API and make things more consistent across the board. The two new features have already been implemented in the dev branch, and I will soon start doing 0.12 beta releases so people can try it out. The breaking changes are pretty much just ideas that I'd like to gather feedback for - in particular, let me know how hard do you think it would be for you to migrate your existing app if these changes went live.

New Features

• async components. Allows defining a component as a function that asynchronous resolves the component definition. This would enable easy lazy-loading mechanisms.
• one-way paramAttributes/props syntax (prop="{{*onetime}}")

Breaking Changes

• paramAttributes renamed to props.
• Intent to remove: v-partial and {{>partial}} syntax. The partial concept is a legacy from string-based templates, and isn't particularly useful when everything should just be components.
• Intent to remove: v-with syntax.
  • It allows the user to add arbitrary data fields to a child component, which may conflict with the child's default data. At the same time, the child needs to be more explicit about what it expects from the parent.
  • It's also confusing to have two ways of doing the same thing. Everything should just be props (previously paramAttributes).
  • The name v-with isn't super precise for what it does now: passing data down to a child. It is also a legacy from string templates that uses {{#with}} blocks to shift the data context.
• Intent to remove: v-component syntax.
  • Similar to v-with, it doesn't make much sense to have two ways of doing the same thing. Every component should just be a custom tag.
  • For dynamic components, use the special <component is="{{view}}"></component> syntax. "component" is a reserved component name.
  • It should no longer be required to have a hyphen in your component name in order to use it as a custom tag.
• Intent to remove: replace option. A component always replaces its placeholder node.
• Intent to remove: inherit option. Prefer explicitly passing down props.

[frolic]

👍

I'm not sure on the proposed inherit changes. I was working on an app where I tried to make use of paramAttributes to keep my components isolated without tight coupling, but ran into issues. I'll see if I can remember or recreate them so I can mention them here.

[thelinuxlich]

Agree with everything minus removing the inherit option.

[taylorotwell]

Looks pretty good overall!

[kazupon]

👍

Among them, I agree especially with removing the v-with directive. because it breaking the child component data.

[nadirabid]

👍

Vue's simple and flexible API is paramount. To be honest, I haven't personally found need for async but I can see it being useful.

Looking forward to 0.12!

[cheapsteak]

Breaking v-with would certainly be a pain to refactor were we to upgrade, but I think it's the right way to go. 👍

[OEvgeny]

Looks pretty good. Except maybe inheritance. But I think with proper props implementation we will not need to inherit all data. Anyway inherit breaks component system, I think.

As I thought one of the partials purposes was to decrease number of complete Vue instances and replace it with something lightweight. Am I wrong? To be honest, didn't use it overall, but it looks useful.

Also Vue documentation is great, but sometimes I need it to be more reach. Any plans for it?

Waiting for 0.12 too!

[ayamflow]

👍 pretty good to see Vue move closer to "real" web components.

[pechorin]

👍

Removing v-with and v-component is great simplification. Also props look's more like react and this is also nice idea.

[crswll]

👍

This all sounds great to me.

[azamat-sharapov]

This is great!!!! Especially async components (which enables lazy loading). I've been spending so many hours to get it work via webpack :D will refactor with pleasure to have lazy loading only from Vue, instead of webpack.

Does "one-way props" have performance advantages? Or it's just for better isolation/protection of prop?

[yyx990803]

@azamat-sharapov performance will be largely the same, it's for better isolation. In some cases you don't want the component to be able to mutate parent state.

[azamat-sharapov]

@yyx990803 thanks. Personally for my projects, if I decide to switch to 0.12, I will have to get rid of v-component, I have been using it since it's not always easy to come up with good name for component without dash. So now dash is not necessary and it's helpful.
Never used partials and always avoid use of inherit since it looks like bad practice to me, so +1 for removing it. And I still have v-with in some places, though I lately got used to paramAttributes and think it's better, so +1 for removing v-with too, even though it requires refactoring for many.

[young-steveo]

@yyx990803 I seem to be in the minority when it comes to v-component; I'm a fan of the <div v-component="{{ view }}"></div> syntax. I never use custom tags in my projects (no strong opinion against custom tags, I just prefer the aesthetics of attributes). This isn't the end of the world, and I love using Vue, so I'll migrate to <dynamic-component type="{{ view }}"></dynamic-component> if this change is set in stone.

Love the idea of async components! 👍

[crswll]

@young-steveo Agreed, but I think it's just us being stubborn. It's definitely going to be the norm in the future.