Evan You e67f655b26 refactor(runtime-core): revert setup() result reactive conversion ... BREAKING CHANGE: revert setup() result reactive conversion Revert 6b10f0c & a840e7d. The motivation of the original change was avoiding unnecessary deep conversions, but that can be achieved by explicitly marking values non-reactive via `markNonReactive`. Removing the reactive conversion behavior leads to an usability issue in that plain objects containing refs (which is what most composition functions will return), when exposed as a nested property from `setup()`, will not unwrap the refs in templates. This goes against the "no .value in template" intuition and the only workaround requires users to manually wrap it again with `reactive()`. So in this commit we are reverting to the previous behavior where objects returned from `setup()` are implicitly wrapped with `reactive()` for deep ref unwrapping.		2020-02-26 19:01:42 -05:00
..
defineComponent.test-d.tsx	refactor(runtime-core): revert setup() result reactive conversion	2020-02-26 19:01:42 -05:00
h.test-d.ts	refactor(createComponent): rename to defineComponent (#549)	2019-12-22 10:58:12 -05:00
index.d.ts	types: fix dts	2019-11-22 18:09:26 -05:00
ref.test-d.ts	test: add type test for nested refs in ref.value	2020-02-25 20:38:09 -05:00
tsx.test-d.tsx	types: fix tsx dts tests	2020-02-15 21:48:45 -05:00
watch.test-d.ts	fix(types): ref value type unwrapping should happen at creation time	2020-02-25 19:44:06 -05:00