Skip to content

Commit 6826c72

Browse files
committed
Remove 'jet-' component prefix from examples
1 parent b87a2f4 commit 6826c72

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

Diff for: 3.x/features/password-confirmation.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -115,11 +115,11 @@ If you are using the Livewire stack, the Livewire component that contains the ac
115115
Next, in your application's user interface, you should wrap the button that triggers the action within the `confirms-password` Blade component. The `confirms-password` wrapper component should contain a `wire:then` directive that specifies which Livewire action should be run once the user's password has been confirmed:
116116

117117
```html
118-
<x-jet-confirms-password wire:then="enableAdminMode">
119-
<x-jet-button type="button" wire:loading.attr="disabled">
118+
<x-confirms-password wire:then="enableAdminMode">
119+
<x-button type="button" wire:loading.attr="disabled">
120120
{{ __('Enable') }}
121-
</x-jet-button>
122-
</x-jet-confirms-password>
121+
</x-button>
122+
</x-confirms-password>
123123
```
124124

125125
#### Ensuring The Password Is Confirmed

Diff for: 3.x/stacks/livewire.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In addition, Jetstream includes two types of modals: `dialog-modal` and `confirm
3636
To illustrate the use of modals, consider the following modal that confirms a user would like to delete their account:
3737

3838
```html
39-
<x-jet-confirmation-modal wire:model="confirmingUserDeletion">
39+
<x-confirmation-modal wire:model="confirmingUserDeletion">
4040
<x-slot name="title">
4141
Delete Account
4242
</x-slot>
@@ -46,15 +46,15 @@ To illustrate the use of modals, consider the following modal that confirms a us
4646
</x-slot>
4747

4848
<x-slot name="footer">
49-
<x-jet-secondary-button wire:click="$toggle('confirmingUserDeletion')" wire:loading.attr="disabled">
49+
<x-secondary-button wire:click="$toggle('confirmingUserDeletion')" wire:loading.attr="disabled">
5050
Nevermind
51-
</x-jet-secondary-button>
51+
</x-secondary-button>
5252

53-
<x-jet-danger-button class="ml-2" wire:click="deleteUser" wire:loading.attr="disabled">
53+
<x-danger-button class="ml-2" wire:click="deleteUser" wire:loading.attr="disabled">
5454
Delete Account
55-
</x-jet-danger-button>
55+
</x-danger-button>
5656
</x-slot>
57-
</x-jet-confirmation-modal>
57+
</x-confirmation-modal>
5858
```
5959

6060
As you can see, the modal's open / close state is determined by a `wire:model` property that is declared on the component. The property's name should correspond to a boolean property on your Livewire component's corresponding PHP class. Typically, you will set this property to `true` when the user clicks a UI element in your application that should open the modal. Of course, the property should be set to `false` when you are ready to close the modal.

0 commit comments

Comments
 (0)