New rule order-in-components

[michalsnik]

This PR adds new rule regarding this proposition: #13

This rule will be applied on:

• export default {} inside .vue and .jsx files
• new Vue({}) in any file
• Vue.component('xxx', {}) or component('xxx', {}) in any file

Thing to be noted - we won't support dynamically loaded components, as it's not so obvious to tell if it actually is or is not a vue component.

[mysticatea]

I guess that this line can throw TypeError if component() with no argument exists.

[michalsnik]

Good point, but I couldn't imagine such a component though. Fixed it anyway :)

[mysticatea]

Many people use ESLint in editor integrations. In that case, ESLint runs on every character typing, so TypeErrors mess development experience. 😉

[mysticatea]

Same here.

[michalsnik]

Fixed

[mysticatea]

I guess that this line can cause TypeError if default exports without object literals (e.g. export default 777) exists.

[michalsnik]

Very good point! Fixed :)

[mysticatea]

LGTM.

[mysticatea]

I think that it needs major version if we keep recommended: true.

[michalsnik]

yeah, I was thinking the same. So maybe we'll wait with this until other PR's are merged, and then we'll bump to 4.0.0. If it will be quite stable - then we could finally release it without the beta tag.

[michalsnik]

I removed recommended setting and will release it as minor atm. We'll update this setting in a while @mysticatea

[privatenumber]

@michalsnik Will this eventually have support for components that were assigned to a variable, and then exported? eg.

const ComponentName = {
     name: 'ComponentName',
     render(h) { return h('div'); }
};

export default ComponentName;

[privatenumber]

@michalsnik

[michalsnik]

I'm not sure yet @hirokiosame. Theoretically we could support this case, and one when you only use that component in current template, but don't even export it. But this needs further investigation, so feel free to create a proposition as separate issue.