Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit a8b4701

Browse files
feat: added compiler flags
1 parent 2ccd26c commit a8b4701

File tree

8 files changed

+23
-4
lines changed

8 files changed

+23
-4
lines changed

src/guide/migration/array-refs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,4 +73,7 @@ Note that:
7373

7474
## Migration Strategy
7575

76-
[Migration build flag: `V_FOR_REF`](migration-build.html)
76+
[Migration build flags:](migration-build.html)
77+
78+
- `V_FOR_REF`
79+
- `COMPILER_V_FOR_REF`

src/guide/migration/custom-elements-interop.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,8 @@ In 3.0, we are limiting Vue's special treatment of the `is` prop to the `<compon
9696
document.createElement('button', { is: 'plastic-button' })
9797
```
9898

99+
[Migration build flag: `COMPILER_IS_ON_ELEMENT`](migration-build.html)
100+
99101
## `v-is` for In-DOM Template Parsing Workarounds
100102

101103
> Note: this section only affects cases where Vue templates are directly written in the page's HTML.

src/guide/migration/filters.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,10 @@ Using the example above, here is one example of how it could be implemented.
7373

7474
Instead of using filters, we recommend replacing them with computed properties or methods.
7575

76-
[Migration build flag: `FILTERS`](migration-build.html)
76+
[Migration build flags:](migration-build.html)
77+
78+
- `FILTERS`
79+
- `COMPILER_FILTERS`
7780

7881
### Global Filters
7982

src/guide/migration/inline-template-attribute.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ This feature will no longer be supported.
3030

3131
Most of the use cases for `inline-template` assumes a no-build-tool setup, where all templates are written directly inside the HTML page.
3232

33+
[Migration build flag: `COMPILER_INLINE_TEMPLATE`](migration-build.html)
34+
3335
### Option #1: Use `<script>` tag
3436

3537
The most straightforward workaround in such cases is using `<script>` with an alternative type:

src/guide/migration/v-bind.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ When dynamically binding attributes on an element, a common scenario involves us
1616

1717
## 2.x Syntax
1818

19-
In 2.x, if an element has both `v-bind="object"` and an identical individual property defined, the individual property would always overwrite bindings in the `object`.
19+
In 2.x, if an element has both `v-bind="object"` and an identical individual property defined, the individual property would always overwrite bindings in the `object`.
2020

2121
```html
2222
<!-- template -->
@@ -44,3 +44,5 @@ In 3x, if an element has both `v-bind="object"` and an identical individual prop
4444
## Migration Strategy
4545

4646
If you are relying on this override functionality for `v-bind`, we currently recommend ensuring that your `v-bind` attribute is defined before individual properties.
47+
48+
[Migration build flag: `COMPILER_V_BIND_OBJECT_ORDER`](migration-build.html)

src/guide/migration/v-if-v-for.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ It is recommended to avoid using both on the same element due to the syntax ambi
2828

2929
Rather than managing this at the template level, one method for accomplishing this is to create a computed property that filters out a list for the visible elements.
3030

31+
[Migration build flag: `COMPILER_V_IF_V_FOR_PRECEDENCE`](migration-build.html)
32+
3133
## See also
3234

3335
- [List Rendering - Displaying Filtered/Sorted Results](/guide/list.html#displaying-filtered-sorted-results)

src/guide/migration/v-model.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,10 @@ We recommend:
182182
}
183183
```
184184

185-
[Migration build flag: `COMPONENT_V_MODEL`](migration-build.html)
185+
[Migration build flags:](migration-build.html)
186+
187+
- `COMPONENT_V_MODEL`
188+
- `COMPILER_V_BIND_SYNC`
186189

187190
## Next Steps
188191

src/guide/migration/v-on-native-modifier-removed.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@ Consequently, Vue will now add all event listeners that are _not_ defined as com
4949
- remove all instances of the `.native` modifier.
5050
- ensure that all your components document their events with the `emits` option.
5151

52+
[Migration build flag: `COMPILER_V_ON_NATIVE`](migration-build.html)
53+
5254
## See also
5355

5456
- [Relevant RFC](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0031-attr-fallthrough.md#v-on-listener-fallthrough)

0 commit comments

Comments
 (0)