6.0.0

Author: rawilk

CHANGELOG.md

@@ -9,12 +9,14 @@ All notable changes to `laravel-form-components` will be documented in this file
 ### Updated
 - Update asset versions in the config
 - Reference all `form-components` components using `<x-form-components::>` instead of `<x-dynamic-component>`
+- Add better support for multi `custom-select` in non-livewire forms ([#34](https://github.com/rawilk/laravel-form-components/issues/34))
 
 ### Changed
 - Switch from rollup to laravel-mix for compiling package JavaScript
 
 ### Breaking changes
-- Increase minimum Laravel version to `8.58`
+- Increase minimum Laravel version to `8.56`
+- Remove ability to override component views in the config (in favor of just publishing the package's views)
 
 ## 5.1.0 - 2021-07-26
 ### Added

docs/_index.md

@@ -1,5 +1,5 @@
 ---
-title: v5
+title: v6
 slogan: A set of Blade components for TailwindCSS forms.
 githubUrl: https://github.com/rawilk/laravel-form-components
 branch: main

docs/installation.md

@@ -65,7 +65,7 @@ Libraries are only loaded for components that are enabled through the `component
 
 ## Views
 
-You may override the views, either by using your own views and specifying them in the config, or by publishing the package's views:
+You may override the views, by publishing the package's views:
 
 ```bash
 php artisan fc:publish --views
@@ -98,10 +98,20 @@ only load the components you need in your app for performance reasons. To do so,
 first [publish the config file](#configuration), then remove the components
 you don't need from the `components` settings.
 
-You can also choose to use different classes and views for components. This allows you
+You can also choose to use different classes for components. This allows you
 to either extend or completely change the component's functionality by using a custom class
 and/or view of your own.
 
+### Component Namespace
+New in v6, the package also declares a `form-components` blade component namespace. This means that
+for any component you may also use the `<x-form-components::component-name>` syntax. For the `input`
+component, you would use `<x-form-components::inputs.input />`. If you choose to render the components
+using this method, you can safely remove the component alias from the config, however there are two caveats to this:
+
+1. You may not be able to override the component class definition any more if you remove the alias from the config.
+2. Some components have an array of configuration options attached to their alias. Those arrays are referenced
+by the component, so these aliases should not be removed or renamed.
+
 ## Component JavaScript
 
 Some components, such as the [custom select component](/docs/laravel-form-components/{version}/selects/custom-select), require custom

docs/requirements.md

@@ -6,14 +6,15 @@ sort: 2
 ## General Requirements
 
 -   PHP **8.0** or greater
--   Laravel **8.0** or greater
+-   Laravel **8.56** or greater
 -   TailwindUI for styling
 -   Alpine.js
 -   Popper.js (when using components like custom-select)
--   Blade Heroicons (can easily swap for icon libraries)
+-   Blade Heroicons (can easily swap for other icon libraries)
 
 ## Version Matrix
 
-| Laravel | Minimum Version |
-| ------- | --------------- |
-| 8.0     | 1.0.0           |
+| Laravel | Minimum Version | Maximum Version |
+| ------- | --------------- | --- |
+| 8.0 - 8.55    | 1.0.0           | 5.1.0 |
+| 8.56 | 6.0.0 | |

docs/upgrade.md

@@ -3,6 +3,20 @@ title: Upgrade
 sort: 4
 ---
 
+## Upgrading from v5 to v6
+
+### Laravel Version
+v6 of laravel-form-components now requires a minimum Laravel version of `8.56`. Be sure to update your project to at least that version.
+
+### Overriding component views
+In v6, you must publish any package views you want to override instead of specifying a different view in the config. This was done to help
+simplify the package config and how the base `BladeComponent` class determines the view to render. You are still free to override any
+component classes in the config, however.
+
+### New Component Namespace
+Not a breaking change, but the package now defines the `form-components` namespace in addition to providing aliases for each component
+in the config. You will now be able to reference components either as `<x-form>` or as `<x-form-components::form>` if you choose to.
+
 ## Upgrading from v4 to v5
 
 ### Alpine upgrade