diff --git a/packages/actions/docs/04-modals.md b/packages/actions/docs/04-modals.md index 2115225021..dc6ac1c102 100644 --- a/packages/actions/docs/04-modals.md +++ b/packages/actions/docs/04-modals.md @@ -19,7 +19,7 @@ Action::make('delete') -> Note: The confirmation modal is not available when a `url()` is set instead of an `action()`. Instead, you should redirect to the URL within the `action()` closure. +> The confirmation modal is not available when a `url()` is set instead of an `action()`. Instead, you should redirect to the URL within the `action()` closure. ## Modal forms @@ -332,7 +332,7 @@ Action::make('create') }) ``` -Please note that the `mountUsing()` method, by default, is used by Filament to initialize the [form](#modal-forms). If you override this method, you will need to call `$form->fill()` to ensure the form is initialized correctly. If you wish to populate the form with data, you can do so by passing an array to the `fill()` method, instead of [using `fillForm()` on the action itself](#filling-the-form-with-existing-data). +> The `mountUsing()` method, by default, is used by Filament to initialize the [form](#modal-forms). If you override this method, you will need to call `$form->fill()` to ensure the form is initialized correctly. If you wish to populate the form with data, you can do so by passing an array to the `fill()` method, instead of [using `fillForm()` on the action itself](#filling-the-form-with-existing-data). ## Customizing the action buttons in the footer of the modal diff --git a/packages/forms/docs/03-fields/01-getting-started.md b/packages/forms/docs/03-fields/01-getting-started.md index 1338862246..a6cbc7a8f8 100644 --- a/packages/forms/docs/03-fields/01-getting-started.md +++ b/packages/forms/docs/03-fields/01-getting-started.md @@ -227,7 +227,7 @@ Toggle::make('is_admin') ->dehydrated() ``` -Please note that if you choose to dehydrate the field, a skilled user could still edit the field's value by manipulating Livewire's JavaScript. +> If you choose to dehydrate the field, a skilled user could still edit the field's value by manipulating Livewire's JavaScript. ### Hiding a field diff --git a/packages/forms/docs/03-fields/09-file-upload.md b/packages/forms/docs/03-fields/09-file-upload.md index 20da1e45eb..5d4d148955 100644 --- a/packages/forms/docs/03-fields/09-file-upload.md +++ b/packages/forms/docs/03-fields/09-file-upload.md @@ -21,7 +21,7 @@ FileUpload::make('attachment') By default, files will be uploaded publicly to your storage disk defined in the [configuration file](../installation#publishing-configuration). You can also set the `FILAMENT_FILESYSTEM_DISK` environment variable to change this. -> Please note, to correctly preview images and other files, FilePond requires files to be served from the same domain as the app, or the appropriate CORS headers need to be present. Ensure that the `APP_URL` environment variable is correct, or modify the [filesystem](https://laravel.com/docs/10.x/filesystem) driver to set the correct URL. If you're hosting files on a separate domain like S3, ensure that CORS headers are set up. +> To correctly preview images and other files, FilePond requires files to be served from the same domain as the app, or the appropriate CORS headers need to be present. Ensure that the `APP_URL` environment variable is correct, or modify the [filesystem](https://laravel.com/docs/10.x/filesystem) driver to set the correct URL. If you're hosting files on a separate domain like S3, ensure that CORS headers are set up. To change the disk and directory for a specific field, and the visibility of files, use the `disk()`, `directory()` and `visibility()` methods: @@ -34,7 +34,7 @@ FileUpload::make('attachment') ->visibility('private') ``` -> Please note, it is the responsibility of the developer to delete these files from the disk if they are removed, as Filament is unaware if they are depended on elsewhere. One way to do this automatically is observing a [model event](https://laravel.com/docs/eloquent#events). +> It is the responsibility of the developer to delete these files from the disk if they are removed, as Filament is unaware if they are depended on elsewhere. One way to do this automatically is observing a [model event](https://laravel.com/docs/eloquent#events). ## Uploading multiple files diff --git a/packages/forms/docs/03-fields/12-repeater.md b/packages/forms/docs/03-fields/12-repeater.md index 9155857c59..accb563185 100644 --- a/packages/forms/docs/03-fields/12-repeater.md +++ b/packages/forms/docs/03-fields/12-repeater.md @@ -447,4 +447,4 @@ Repeater::make('members') ) ``` -Please note that the `collapseAction()`, `collapseAllAction()`, `expandAction()`, `expandAllAction()` and `reorderAction()` methods do not support confirmation modals, as clicking their buttons does not make the network request that is required to show the modal. +> The `collapseAction()`, `collapseAllAction()`, `expandAction()`, `expandAllAction()` and `reorderAction()` methods do not support confirmation modals, as clicking their buttons does not make the network request that is required to show the modal. diff --git a/packages/forms/docs/03-fields/13-builder.md b/packages/forms/docs/03-fields/13-builder.md index 764fa255f5..bfef8af1d5 100644 --- a/packages/forms/docs/03-fields/13-builder.md +++ b/packages/forms/docs/03-fields/13-builder.md @@ -350,4 +350,4 @@ Builder::make('content') ) ``` -Please note that the `addAction()`, `addBetweenAction()`, `collapseAction()`, `collapseAllAction()`, `expandAction()`, `expandAllAction()` and `reorderAction()` methods do not support confirmation modals, as clicking their buttons does not make the network request that is required to show the modal. +> The `addAction()`, `addBetweenAction()`, `collapseAction()`, `collapseAllAction()`, `expandAction()`, `expandAllAction()` and `reorderAction()` methods do not support confirmation modals, as clicking their buttons does not make the network request that is required to show the modal. diff --git a/packages/forms/docs/07-advanced.md b/packages/forms/docs/07-advanced.md index 8491e0aef1..5f49a910d4 100644 --- a/packages/forms/docs/07-advanced.md +++ b/packages/forms/docs/07-advanced.md @@ -230,7 +230,7 @@ TextInput::make('name') ### Field updates -You may use the `afterStateUpdated()` method to customize what happens after a field is updated by the user. Please note that only changes from the user on the frontend will trigger this function, not manual changes to the state from `$set()` or another PHP function. +You may use the `afterStateUpdated()` method to customize what happens after a field is updated by the user. Only changes from the user on the frontend will trigger this function, not manual changes to the state from `$set()` or another PHP function. Inside this function, you can also inject the `$old` value of the field before it was updated, using the `$old` parameter: diff --git a/packages/forms/docs/08-adding-a-form-to-a-livewire-component.md b/packages/forms/docs/08-adding-a-form-to-a-livewire-component.md index e7d8d63030..1cebc381ae 100644 --- a/packages/forms/docs/08-adding-a-form-to-a-livewire-component.md +++ b/packages/forms/docs/08-adding-a-form-to-a-livewire-component.md @@ -100,7 +100,7 @@ Finally, in your Livewire component's view, render the form: ``` -> Note: `` is used to render form component [action modals](actions). The code can be put anywhere outside of the `
` element, as long as it's within the Livewire component. +> `` is used to render form component [action modals](actions). The code can be put anywhere outside of the `` element, as long as it's within the Livewire component. Visit your Livewire component in the browser, and you should see the form components from `schema()`: @@ -336,4 +336,4 @@ Now, you can use the `--generate` flag when generating your form: php artisan make:livewire-form Products/CreateProduct --generate ``` -> Note: If your table contains ENUM columns, `doctrine/dbal` is unable to scan your table and will crash. Hence Filament is unable to generate the schema for your table if it contains an ENUM column. Read more about this issue [here](https://github.com/doctrine/dbal/issues/3819#issuecomment-573419808). +> If your table contains ENUM columns, `doctrine/dbal` is unable to scan your table and will crash. Hence Filament is unable to generate the schema for your table if it contains an ENUM column. Read more about this issue [here](https://github.com/doctrine/dbal/issues/3819#issuecomment-573419808). diff --git a/packages/panels/docs/03-resources/01-getting-started.md b/packages/panels/docs/03-resources/01-getting-started.md index c3a97034b7..72a768dc21 100644 --- a/packages/panels/docs/03-resources/01-getting-started.md +++ b/packages/panels/docs/03-resources/01-getting-started.md @@ -60,7 +60,7 @@ When creating your resource, you may now use `--generate`: php artisan make:filament-resource Customer --generate ``` -> Note: If your table contains ENUM columns, `doctrine/dbal` is unable to scan your table and will crash. Hence Filament is unable to generate the schema for your resource if it contains an ENUM column. Read more about this issue [here](https://github.com/doctrine/dbal/issues/3819#issuecomment-573419808). +> If your table contains ENUM columns, `doctrine/dbal` is unable to scan your table and will crash. Hence Filament is unable to generate the schema for your resource if it contains an ENUM column. Read more about this issue [here](https://github.com/doctrine/dbal/issues/3819#issuecomment-573419808). ### Handling soft deletes diff --git a/packages/panels/docs/03-resources/08-global-search.md b/packages/panels/docs/03-resources/08-global-search.md index 1a3f0b0f04..26f28972a5 100644 --- a/packages/panels/docs/03-resources/08-global-search.md +++ b/packages/panels/docs/03-resources/08-global-search.md @@ -16,7 +16,7 @@ protected static ?string $recordTitleAttribute = 'title'; This attribute is used to retrieve the search result title for that record. -**Note:** Your resource needs to have an Edit or View page to allow the global search results to link to a URL, otherwise no results will be returned for this resource. +> Your resource needs to have an Edit or View page to allow the global search results to link to a URL, otherwise no results will be returned for this resource. You may customize the title further by overriding `getGlobalSearchResultTitle()` method: diff --git a/packages/panels/docs/03-resources/10-custom-pages.md b/packages/panels/docs/03-resources/10-custom-pages.md index d092de14b3..c048d85afa 100644 --- a/packages/panels/docs/03-resources/10-custom-pages.md +++ b/packages/panels/docs/03-resources/10-custom-pages.md @@ -24,6 +24,6 @@ public static function getPages(): array } ``` -Please note that the order of pages registered in this method matters - any wildcard route segments that are defined before hard-coded ones will be matched by Laravel's router first. +> The order of pages registered in this method matters - any wildcard route segments that are defined before hard-coded ones will be matched by Laravel's router first. Any [parameters](https://laravel.com/docs/routing#route-parameters) defined in the route's path will be available to the page class, in an identical way to [Livewire](https://laravel-livewire.com/docs/rendering-components#route-params). diff --git a/packages/tables/docs/07-summaries.md b/packages/tables/docs/07-summaries.md index ac4200f512..94050c33b7 100644 --- a/packages/tables/docs/07-summaries.md +++ b/packages/tables/docs/07-summaries.md @@ -34,7 +34,7 @@ TextColumn::make('rating') ]) ``` -> Note: The first column in a table may not use summarizers. That column is used to render the heading and subheading/s of the summary section. +> The first column in a table may not use summarizers. That column is used to render the heading and subheading/s of the summary section. diff --git a/packages/tables/docs/11-adding-a-table-to-a-livewire-component.md b/packages/tables/docs/11-adding-a-table-to-a-livewire-component.md index 4565d7321a..29e24b60f3 100644 --- a/packages/tables/docs/11-adding-a-table-to-a-livewire-component.md +++ b/packages/tables/docs/11-adding-a-table-to-a-livewire-component.md @@ -113,4 +113,4 @@ Now, you can use the `--generate` flag when generating your table: php artisan make:livewire-table Products/ListProducts --generate ``` -> Note: If your table contains ENUM columns, `doctrine/dbal` is unable to scan your table and will crash. Hence Filament is unable to generate the schema for your table if it contains an ENUM column. Read more about this issue [here](https://github.com/doctrine/dbal/issues/3819#issuecomment-573419808). +> If your table contains ENUM columns, `doctrine/dbal` is unable to scan your table and will crash. Hence Filament is unable to generate the schema for your table if it contains an ENUM column. Read more about this issue [here](https://github.com/doctrine/dbal/issues/3819#issuecomment-573419808).