lunarphp · dewebdesigns · Apr 28, 2023 · May 11, 2023 · May 11, 2023 · May 16, 2023
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,9 @@
 blank_issues_enabled: false
+
 contact_links:
-  - name: Support Questions & Other
-    url: https://github.com/lunarphp/lunar/discussions
-    about: 'If you have a question, or need some support from the community'
+  - name: Feature request
+    url: https://github.com/lunarphp/lunar/discussions/new/choose
+    about: For ideas or feature requests
+  - name: Support questions & other
+    url: https://github.com/lunarphp/lunar/discussions/new/choose
+    about: If you have a question, or need some support from the community
diff --git a/.github/ISSUE_TEMPLATE/enhancement_request.md b/.github/ISSUE_TEMPLATE/enhancement_request.md
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
diff --git a/.github/workflows/static-analysis.yml b/.github/workflows/static-analysis.yml
@@ -0,0 +1,44 @@
+name: "Static Analysis"
+
+on:
+  pull_request:
+
+concurrency:
+  group: sa-${{ github.head_ref || github.run_id }} # will be canceled on subsequent pushes in pull requests but not branches
+  cancel-in-progress: true
+
+jobs:
+  static-analysis:
+    strategy:
+      fail-fast: false
+      matrix:
+        php: ["8.1", "8.2"]
+        laravel: ["^9.0", "^10.0"]
+        dependencies: ["highest"]
+
+    name: "PHP ${{ matrix.php }} - L${{ matrix.laravel }} ${{ matrix.dependencies == 'highest' && '↑' || '↓' }}"
+
+    runs-on: "ubuntu-latest"
+
+    steps:
+      - name: "Checkout code"
+        uses: "actions/checkout@v3"
+
+      - name: "Setup PHP"
+        uses: "shivammathur/setup-php@v2"
+        with:
+          php-version: "${{ matrix.php }}"
+          extensions: "dom, curl, libxml, mbstring, zip, fileinfo"
+          tools: "composer:v2"
+          coverage: "none"
+
+      - name: "Install dependencies from composer.json"
+        if: "matrix.dependencies != 'lowest'"
+        run: "composer update --with='laravel/framework:${{ matrix.laravel }}' --no-interaction --no-progress"
+
+      - name: "Install lowest dependencies from composer.json"
+        if: "matrix.dependencies == 'lowest'"
+        run: "composer update --with='laravel/framework:${{ matrix.laravel }}' --no-interaction --no-progress --prefer-lowest"
+
+      - name: "Run PHPStan"
+        run: ./vendor/bin/phpstan
diff --git a/.gitignore b/.gitignore
@@ -9,3 +9,4 @@ yarn.lock
 package-lock.json
 .DS_Store
 .nova
+phpstan.neon
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-<p align="center"><a href="https://lunarphp.io/" target="_blank"><img src="https://raw.githubusercontent.com/lunarphp/art/main/lunar-logo.svg" width="200" alt="Lunar"></a></p>
+<p align="center"><a href="https://lunarphp.io/" target="_blank"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/lunarphp/art/main/lunar-logo-dark.svg"><img alt="Lunar" width="200" src="https://raw.githubusercontent.com/lunarphp/art/main/lunar-logo.svg"></picture></a></p>
 
 [Lunar](https://lunarphp.io) is a set of Laravel packages that bring functionality akin to Shopify and other e-commerce platforms to Laravel. You have complete freedom to create your own storefront(s), but we've already done the hard work for you in the backend.
 
@@ -14,6 +14,12 @@ This repository serves as a monorepo for the main packages that make up Lunar.
 
 - [Full documentation](https://docs.lunarphp.io/) - Includes in-depth guides on everything Lunar
 
+## Contribution
+
+- Bug reports should be submitted as a new Github issue
+- Enhancements should [https://github.com/lunarphp/lunar/discussions/new?category=enhancements](be in discussions)
+- Feature requests should [https://github.com/lunarphp/lunar/discussions/new?category=feature-requests](be in discussions)
+
 ## Community
 
 - [Join our discord server](https://discord.gg/v6qVWaf) and chat to the developers and people using Lunar.

diff --git a/composer.json b/composer.json
@@ -35,7 +35,8 @@
         "mockery/mockery": "^1.4.4",
         "orchestra/testbench": "^7.0|^8.0",
         "phpunit/phpunit": "^9.5",
-        "symplify/monorepo-builder": "^10.0"
+        "symplify/monorepo-builder": "^10.0",
+        "nunomaduro/larastan": "^2.0"
     },
     "autoload": {
         "files": [

diff --git a/docs/.vitepress/config.js b/docs/.vitepress/config.js
@@ -42,8 +42,7 @@ export default defineConfig({
           { text: 'Livewire Starter Kit', link: 'https://github.com/lunarphp/livewire-starter-kit' },
           { text: 'Add-ons', link: 'https://github.com/lunarphp/awesome' },
           { text: 'Discord', link: 'https://discord.gg/v6qVWaf' },
-          { text: 'Discussions', link: 'https://github.com/lunarphp/lunar/discussions' },
-          { text: 'Roadmap', link: 'https://github.com/orgs/lunarphp/projects/1' }
+          { text: 'Discussions', link: 'https://github.com/lunarphp/lunar/discussions' }
         ]
       },
       {
@@ -70,6 +69,7 @@ export default defineConfig({
             { text: 'Configuration', link: '/core/configuration' },
             { text: 'Initial Set-Up', link: '/core/set-up' },
             { text: 'Upgrade Guide', link: '/core/upgrading' },
+            { text: 'Release Schedule', link: '/core/release-schedule' },
             { text: 'Security', link: '/core/securing-your-site' },
             { text: 'Contributing', link: '/core/contributing' }
           ]

diff --git a/docs/admin-hub/extending.md b/docs/admin-hub/extending.md
@@ -364,7 +364,7 @@ Create a Livewire component to handle your custom discount type.
 
 namespace App\Http\Livewire\Components;
 
-use Illuminate\Support\Facades\DB;
+use Lunar\Facades\DB;
 use Lunar\Models\Discount;
 use Lunar\Hub\Http\Livewire\Components\Discounts\Types\AbstractDiscountType;
 

diff --git a/docs/core/configuration.md b/docs/core/configuration.md
@@ -19,6 +19,23 @@ So that Lunar tables do not conflict with your existing application database tab
     'table_prefix' => 'lunar_',
 ```
 
+### Database Connection
+
+`lunar/database.php`
+
+ By default, the package uses the default database connection defined in Laravel. Here specify a custom database connection for Lunar.
+
+```php
+    'connection' => 'some_custom_connection',
+```
+
+If you are using a custom database connection that is not the default connection in your Laravel configuration, you need to specify it in the .env file as well.
+
+```
+    ACTIVITY_LOGGER_DB_CONNECTION=some_custom_connection
+```
+In our package, we utilize Spatie's [laravel-activitylog](https://spatie.be/docs/laravel-activitylog) for logging. The mentioned configuration allows the activity logger to use a different database connection instead of the default database connection.
+
 ### Orders
 
 `lunar/orders.php`

diff --git a/docs/core/contributing.md b/docs/core/contributing.md
@@ -8,13 +8,13 @@ You can contribute to the project in many different ways. Reporting bugs, fixing
 
 ## Monorepo
 
-Lunar uses a monorepo [lunarphp/lunar](https://github.com/lunarphp/lunar) to house the core, admin hub and documentation. [Monorepos](https://en.wikipedia.org/wiki/Monorepo) are quite common, but may not be familiar to some. The monorepo helps us to organise the code for ease of development.
+Lunar uses a monorepo [lunarphp/lunar](https://github.com/lunarphp/lunar) approach to maintaining its codebase. [Monorepos](https://en.wikipedia.org/wiki/Monorepo) are quite common, but may not be familiar to some. The monorepo helps us to organise the code for ease of development.
 
 ## Repository Branching
 
 **Bug Fixes** should target the latest compatible branch version i.e `0.3`. The `main` branch should never have bug fix PR's unless they fix features that are in an upcoming release.
 
-**Features** should target the `main` branch if they introduce breaking changes, otherwise they can target the latest compatible branch version i.e `0.3`.
+**Features** that bring new (or enhance current) functionality to Lunar should always target the `main` branch.
 
 ## Contributing Code
 
@@ -54,7 +54,7 @@ Open source code belongs to all of us, and it's all of our responsibility to pus
 
 ## Proposing a Feature
 
-Before you start coding away on the next awesome feature, we highly recommend starting a [discussion](https://github.com/lunarphp/lunar/issues/new/choose) to check that your contribution will be welcomed. We would hate for you to spend valuable time on something that won't be merged into Lunar.
+Before you start coding away on the next awesome feature, we highly recommend starting a [discussion](https://github.com/lunarphp/lunar/discussions) to check that your contribution will be welcomed. We would hate for you to spend valuable time on something that won't be merged into Lunar.
 
 However, you're more than welcome to code away on your idea if you think it will help the discussion.
 
@@ -65,8 +65,10 @@ If the pull request is missing information or unclear as to what it offers or so
 
 A PR should be able to include the following:
 
-- Clearly show in the title the version the PR is targeting i.e. `[0.3]` or `[0.4]`.
+- The title should be relevant and quickly explain what to expect inside
 - A clear description of the feature or fix
+- References to any issues the PR resolves
+- Label as either a `bug`, `enhancement`, `feature` or `documentation`
 - Any relevant documentation updates
 - Unit tests with adequate code coverage
 - Changelog entry

diff --git a/docs/core/installation.md b/docs/core/installation.md
@@ -18,11 +18,6 @@
 composer require lunarphp/lunar
 ```
 
-::: tip Laravel 10
-Laravel 10 support is still in beta release. You can install it by targeting `0.3.0-beta`, but it is not considered production ready at this point.
-```sh
-composer require lunarphp/lunar "^0.3.0-beta"
-```
 :::
 
 ### Add the LunarUser Trait

diff --git a/docs/core/overview.md b/docs/core/overview.md
@@ -16,8 +16,6 @@ Although the admin hub uses Laravel Livewire, there is no requirement for your a
 
 Lunar as a company has grand plans to continue developing new functionality to help you build awesome e-commerce websites. We want Lunar to be a true alternative to the likes of Magento, Shopify, WooCommerce, etc.
 
-Keep an eye on [our roadmap](https://github.com/orgs/lunarphp/projects/1) for future plans and recent releases.
-
 ## Get started
 
 Enough waffle! Let's help you [install Lunar...](/core/installation)
diff --git a/docs/core/reference/carts.md b/docs/core/reference/carts.md
@@ -111,7 +111,6 @@ foreach ($cart->discountBreakdown as $discountBreakdown) {
     }
     $discountBreakdown->total->value
 }
-```
 
 foreach ($cart->discountBreakdown as $discountBreakdown) {
     $discountBreakdown->discount_id

diff --git a/docs/core/reference/products.md b/docs/core/reference/products.md
@@ -320,6 +320,12 @@ $taxClass = TaxClass::where(...)->first();
 $currency = Currency::where(...)->first();
 ```
 
+You can also specify a status to limit results to using the provided scope.
+
+```php
+Product::status('published')->get();
+```
+
 Then we need to create our base option and it's values.
 
 ```php
@@ -431,6 +437,19 @@ $price->price->formatted('fr') // 1,99 £GB
 $price->price->formatted('en-gb', \NumberFormatter::SPELLOUT) // one point nine nine.
 ```
 
+If you are using unit quantities in your product pricing, then you may wish to also use the following methods.
+
+```php
+// will give the decimal price for a single unit
+$price->price->unitDecimal  
+
+// will give the decimal price for a single unit, without rounding
+$price->price->unitDecimal(false)  
+
+// will give the formatted price for a single unit
+$price->price->unitFormatted  
+```
+
 ### Base Pricing
 
 Pricing is defined on a variant level, meaning you will have a different price for each variant and also for each currency in the system. In order to add pricing to a variant, you can either create the model directly or use the relationship method.
@@ -568,6 +587,14 @@ $pricing->tiers;
 $pricing->customerGroupPrices;
 ```
 
+Sometimes you might want to simply get all prices a product has from the variants, instead of loading up all a products variants fetching the prices that way, you can use the `prices` relationship on the product.
+
+```php
+$product->prices
+```
+
+This will return a collection of `Price` models.
+
 ## Full Example
 
 For this example, we're going to be creating some Dr. Martens boots. Below is a screenshot of what we're aiming for:

diff --git a/docs/core/release-schedule.md b/docs/core/release-schedule.md
@@ -0,0 +1,37 @@
+# Release Schedule
+
+## Overview
+
+Lunar is currently on a `0.x` version. This means in order to get to a stable `1.0.0` release, we need to go through quite a rapid development cycle to ensure we are delivering bug fixes and features you expect from your e-commerce system.
+
+For this reason we have committed to a release schedule that we feel will communicate what new features you can expect, when they will arrive and when important bug fixes will be released. Also, importantly, contributors will know with a certain level of accuracy when the feature they are proposing will be included and at what version.
+
+### Schedule
+
+- Feature Releases `0.x` - Released at the start of every month
+- Bug Fixes `0.x.x` - Grouped and released at the end of each working week (Friday)
+- Critical/Security Bug Fixes `0.x.x` - Released within the day they are merged.
+
+## Backwards Compatibility and Upgrading
+
+One concern is if we are releasing `0.x` versions frequently, what does this mean for you as the developer in terms of the level of effort required to upgrade for each version, for example `0.2` to `0.3` or `0.2` to `0.5` etc.
+
+For each release there will be a dedicated upgrade section on the [Upgrade Guide](/core/upgrading) page, which will provide the required upgrade steps for you to take.
+
+## Feature Releases (`0.x`)
+
+Minor versions will be released at the start of each month. The `main` branch is considered the "edge" version and will contain features for the next release.
+
+This timeframe will give all contributors enough time to finalise their pull requests and also allow us to test the features to ensure they are ready for release.
+
+Once a new version is released, the previous version will no longer be supported and it will be recommended for all developers to upgrade to the latest version.
+
+:::tip 
+If a bug is found on a previous version that is also present on the latest `0.x` release, it will be fixed in the latest release, unless it is a security issue.
+:::
+
+### Bug fixes (`0.x.x`)
+
+If there are PR's which have been opened to fix bugs, we will generally group them together and do a patch release at the end of the week, depending on volume and level.
+
+Any fixes which are deemed critical will be released as they are merged to ensure everyone benefits straight away. When a release is tagged it will automatically be broadcast to our discord server.
diff --git a/packages/admin/CHANGELOG.md b/packages/admin/CHANGELOG.md
@@ -4,6 +4,30 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
+## 0.3.0
+
+> Latest updates from `0.2` have been brought in.
+
+### Fixed
+
+- The sales dashboard graph now correctly shows figures.
+- When going to a new page on table listings, the page will now scroll to the top.
+- The iframe height on email previews has been increased to avoid cut off.
+- Refactor row selection on tables to avoid extra roundtrips to Livewire.
+- AttributeGroup saving will now pass the id if being edited to prevent false validation exception being thrown.
+- Added a validation check for the product variant backorder.
+
+### Changed
+
+- Dashboard stats are now responsible for their own date ranges where applicable.
+- The tags panel on the order detail screen has been moved below the address details.
+- Brands will now list alphabetically by default.
+- Dimensions are now sorted by the order in the shipping configuration file.
+
+### Added
+
+- Brands are now searchable and can have saved searches.
+
 ## 0.3.0-beta.3
 
 > Maintenance update to bring changes from 0.2.5 in.
@@ -38,6 +62,22 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 - Changed Auth guard to use Laravel's default driver.
 - Updated `db_date` function to return just the formmatted string.
 
+## 0.2.7
+
+### Fixed
+
+- Added missing notification translation.
+- Variant stock level will now be validated correctly to prevent DB exception on save.
+- Variant image uploading will now check for S3 usage when uploading, the same as product saving.
+- When reordering items, the `$index` now checks for an integer instead of purely existence to prevent failure when `$index` is `0`.
+- Improved validation on translatable attributes to prevent exception when entering multiple languages.
+
+## 0.2.6
+
+### Fixed
+
+- When creating an option, `wire:model` should now correctly reference `newProductOption` when editing the name in a different locale.
+
 ## 0.2.5
 
 ### Fixed