-
Notifications
You must be signed in to change notification settings - Fork 4.7k
3.2 updates #1157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.2 updates #1157
Conversation
yyx990803
commented
Aug 3, 2021
- Added dedicated API pages for SFC spec, tooling & features
- Added "Vue and Web Components" section
- various 3.2 features
- Updated Single File Components guide section - Added dedicated SFC spec & tooling sections in API references - Added dedicated API references for `<script setup>` and `<style>` features
src/api/sfc-script-setup.md
Outdated
|
||
- In dev mode, the compiler will try to infer corresponding runtime validation from the types. For example here `foo: String` is inferred from the `foo: string` type. If the type is a reference to an imported type, the inferred result will be `foo: null` (equal to `any` type) since the compiler does not have information of external files. | ||
|
||
- In prod mode, the compiler will generate the array format declaration to reduce bundle size (the props here will be compiled into `['msg']`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know this! 🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yyx990803 great work! I've added a bunch of minor nitpicks here and there
# Effect Scope API <Badge text="3.2+" /> | ||
|
||
:::info | ||
Effect scope is an advanced API primarily intended for library authors. For details on how to leverage this API, please consult its corresponding [RFC](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0041-reactivity-effect-scope.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yyx990803 should we eventually move the RFC to the Guide section of the docs? Definitely not the scope of the current PR but we can create a follow-up after 3.2 is released
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe. I want to think about where it should be fit into the doc structure though, maybe a section for "advanced reactivity patterns".
Co-authored-by: Natalia Tepluhina <[email protected]> Co-authored-by: Adrià Fontcuberta <[email protected]> Co-authored-by: Eduardo San Martin Morote <[email protected]>
Co-authored-by: Eduardo San Martin Morote <[email protected]> Co-authored-by: Jeff Yang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some suggested tweaks from me. Let me know if anything I've suggested needs clarification.
Co-authored-by: skirtle <[email protected]> Co-authored-by: Jeff Yang <[email protected]>
@yyx990803 Should this PR be targeting |
@bencodezen this should land on |