keep consistency in dev and prod env

[jingsam]

No description provided.

[yyx990803]

Does this cause any problem in production?

[jingsam]

Noop, I just thought that vue should have the same behaviour in development and production enviroment except extra warnings.

[jingsam]

One more thing, I think this line of code should be deleted in Vue 2. In vue 1, name will be used as a function name, such as:
name='MyComponent' => function MyComponent () {this._init(options)}
However, in Vue 2, no matter what the name is, always use function VueComponent() {this._init(options)}

[yyx990803]

@jingsam true, I think this PR can be changed to simply removing that line.

[jingsam]

Ops, CI failed in this test:`

  it('when incorrect name given it should not contain itself in self components', () => {
    const vm = Vue.extend({
      name: 'Hyper*Vue'
    })

    expect(vm.options.components['Hyper*Vue']).toBeUndefined()

In fact, in Vue 2, there are no limitations on the name of components. Even invalid name can be registered. The only limitation is whether the virtual dom can parse the name tag into the corresponding component. For example, Hyper*Vue can be registered but <Hyper*Vue></Hyper*Vue> can not be parsed by virtual dom correctly. _HyperVue is an invalid name but it works, as <_HyperVue></_HyperVue> can be parsed.

@yyx990803 so, shall I delete that unit test case ?

[yyx990803]

Yeah, I think that test case can be removed.