Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Natalia Tepluhina <[email protected]>
  • Loading branch information
ikxin and NataliaTepluhina committed Jun 1, 2023
1 parent 8dfbd25 commit 33b9884
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion src/api/options-misc.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ Controls whether the default component attribute fallthrough behavior should be
</template>
```

Since 3.3 you can also use defineOptions directly in script setup, no longer need normal `<script>` block.
Since 3.3 you can also use `defineOptions` directly in `<script setup>`:

```vue
<script setup>
Expand Down
2 changes: 1 addition & 1 deletion src/guide/components/attrs.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ export default {
</script>
```

Since 3.3 you can also use defineOptions directly in script setup, no longer need normal `<script>` block.
Since 3.3 you can also use `defineOptions` directly in `<script setup>`:

```vue
<script setup>
Expand Down
2 changes: 1 addition & 1 deletion src/guide/extras/composition-api-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ Yes in terms of stateful logic. When using Composition API, there are only a few

:::tip

Since 3.3 you can directly use defineOptions in `<script setup>` to set name or inheritAttrs.
Since 3.3 you can directly use `defineOptions` in `<script setup>` to set the component name or `inheritAttrs` property

:::

Expand Down

0 comments on commit 33b9884

Please sign in to comment.