From 4965306d46f938937e21c88bdae63ed17b4207f8 Mon Sep 17 00:00:00 2001 From: birchb Date: Sat, 27 Oct 2018 16:56:23 -0400 Subject: [PATCH] Update stepper.md I cleaned up some of the grammar in lines 134 - 136 to clarify how the code works, and grouped the sentences differently for clarity. --- source/components/stepper.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/components/stepper.md b/source/components/stepper.md index 8af1e15d..1dd40b79 100644 --- a/source/components/stepper.md +++ b/source/components/stepper.md @@ -131,9 +131,9 @@ Component events: | `@step` | Emitted when navigating to another step. | ### Using `v-model` -Each QStep has a `name` prop (which is optional). Use this prop along with `v-model` to control the current step. +Each QStep has an optional `name` prop. Use the `@click` to set the value of `currentStep` in `v-model`. The example below shows how you can use `v-model` alone to control navigation using `@click` events. -The example below shows how you can use `v-model` alone to control navigation. Notice the `@click` events. If you dynamically insert/remove Steps it's better to use a Vue reference on QStepper and call `next()` or `previous()` methods since these methods are not binded to specific Step names. +If you dynamically insert/remove steps, then it's better to use a Vue reference on QStepper ($refs.stepper) and call the `next()` or `previous()` methods since these methods are not bound to specific step names. ```html