theluyuan/vue3-yuanma
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1,574 Commits 1 Branch 0 Tags 21 MiB
TypeScript 97%
HTML 1.4%
JavaScript 1.1%
Vue 0.5%
e67f655b26
Go to file
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
.circleci ci: bust cache 2019-12-20 10:59:21 -05:00
.github chore: fixes a small typo and prettifies the document (#778) 2020-02-26 10:11:49 -05:00
.vscode workflow: support debug single jest test file in vscode (#360) 2019-10-23 11:20:05 -04:00
packages refactor(runtime-core): revert setup() result reactive conversion 2020-02-26 19:01:42 -05:00
scripts build: remove compiler-ssr and server-renderer from skipped packages 2020-02-18 14:56:53 -05:00
test-dts refactor(runtime-core): revert setup() result reactive conversion 2020-02-26 19:01:42 -05:00
.gitignore chore: add the yarn error log file to git ignore (#150) 2019-10-09 12:13:54 -04:00
.prettierrc init (graduate from prototype) 2018-09-19 11:35:38 -04:00
api-extractor.json chore: config comments 2019-09-03 12:17:33 -04:00
CHANGELOG.md release: v3.0.0-alpha.7 2020-02-26 14:36:38 -05:00
jest.config.js build: avoid runtime wildcard import in global build 2020-02-13 18:50:36 -05:00
LICENSE chore: license 2019-10-28 11:15:17 -04:00
package.json release: v3.0.0-alpha.7 2020-02-26 14:36:38 -05:00
README.md chore: readme 2020-02-18 14:56:53 -05:00
rollup.config.js build: use buildOption to determine runtime compile build (#742) 2020-02-19 09:50:24 -05:00
tsconfig.json test(ssr): test for rendering components 2020-01-29 16:46:18 -05:00
yarn.lock build(deps-dev): bump @types/puppeteer from 2.0.0 to 2.0.1 2020-02-26 07:49:39 +00:00

README.md

vue-next CircleCI

Status: Alpha.

The current codebase has basic feature parity with v2.x, together with the changes proposed in merged RFCs. There is a simple webpack-based setup with Single-File Component support available here.

Please note that there could still be undocumented behavior inconsistencies with 2.x. When you run into such a case, please make sure to first check if the behavior difference has already been proposed in an existing RFC. If the inconsistency is not part of an RFC, then it's likely unintended, and an issue should be opened (please make sure to use the issue helper when opening new issues).

TODOs as of 3.0.0-alpha.5

  • Suspense support in SSR
  • SSR Hydration mismatch handling
  • SSR vnode directive support
  • SSR integration tests
  • 2.x compatible async component support

Known Issues

  • There is currently no way to attach custom instance properties via Vue.prototype.

  • The current implementation requires native ES2015+ in the runtime environment and does not support IE11 (yet).

Contribution

See Contributing Guide.