Fixed lifecycle twice executing (close #1742)

[kazupon]

What I did

Fixed #1742

How to test

$ yarn bootstrap --core
$ yarn link
$ cd apps/vue
$ yarn link
$ cd ../../examples/vue-kitchen-sink
$ edit src/stories/Button.vue

add the below created hook:

created() [
  console.log('call created hook');
}

$ yarn run storybook

On the browser, the below actions

• open inspect panel of devtools
• select console tab
• rounted Select [Button] of manager panel on Storybook
• page reload storybook page

After that, in the output of the console, output call created hook once only

[codecov]

Codecov Report

Merging #1983 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1983   +/-   ##
=======================================
  Coverage   21.34%   21.34%           
=======================================
  Files         262      262           
  Lines        5767     5767           
  Branches      696      705    +9     
=======================================
  Hits         1231     1231           
+ Misses       4005     3987   -18     
- Partials      531      549   +18

Impacted Files	Coverage Δ
app/vue/src/client/preview/render.js	0% <ø> (ø)	⬆️
lib/ui/src/modules/ui/libs/hierarchy.js	48.8% <0%> (ø)	⬆️
lib/ui/src/modules/ui/containers/down_panel.js	23.52% <0%> (ø)	⬆️
app/react/src/client/preview/error_display.js	0% <0%> (ø)	⬆️
lib/ui/src/modules/ui/routes.js	0% <0%> (ø)	⬆️
addons/knobs/src/components/types/Boolean.js	11.62% <0%> (ø)	⬆️
addons/info/src/components/Node.js	39.7% <0%> (ø)	⬆️
lib/ui/src/modules/ui/containers/layout.js	12.5% <0%> (ø)	⬆️
.../ui/src/modules/ui/components/layout/dimensions.js	15.62% <0%> (ø)	⬆️
.../ui/src/modules/ui/components/left_panel/header.js	29.62% <0%> (ø)	⬆️
... and 24 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dde82cf...baddc70. Read the comment docs.

[ndelangen]

Is this not also a valid change for react? totally guessing here.

either way this PR is good to merge, as it addresses a very nasty bug for Vue users!

[kazupon]

yup, In the Vue, occure the similar issues.