This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.

Before merging, you need to:

• Checkout the shift-66727 branch
• Run composer update
• Run npm install
• Review all comments for additional changes
• Thoroughly test your application (no tests?, no CI?)

Please send your feedback to [email protected] or share the good vibes on Twitter.

• Multi Stage Dockerization for reduce docker image size.
• Support php-fpm Customisable
• Support nginx Customisable
• Easily update port
• No dependency
• No need to install laravel-sail

Step to reproduce:

• Go filament demo, choose whatever page from sidebar (products, orders, etc).
• As error doesn't always happened, try to search: 576674888648395525 or similar to ensure you catch the error.
• Refresh the page (with the table search url query still there)
• Clear or modify the search bar and an error will pop up (please check the error log, my app showed a livewire error)

https://user-images.githubusercontent.com/26832856/194875421-658223bb-101b-4785-b8a9-61aa7c6019c7.mp4

I have actually seen this a few times before. I assumed maybe it was a rate limit. Probably someone is currently updating it, but might be worth exploring if it can deployed with less downtime?

Sqlite does not have a native CONCAT function. However it does have the capability with a different syntax. This PR allows selectively checks if you are running the migrations against Sqlite and changes the virtual full_address column to work it's unique syntax.

This demo is very well designed, and it would be neat to be able to use components from it. However, since there is no license file attached, no-one is allowed to use the code herein. https://choosealicense.com/no-permission/

I would suggest the MIT License, as that's what both Laravel and FilamentPHP uses.

All the best, Caen

Package

filament/filament

Package Version

have no idea

Laravel Version

have no idea

Livewire Version

have no idea

PHP Version

have no idea

Bug description

1. In the above image, you can see in number fields 'e' keywords allowing me but others alphabet not to input ...there should not be allowed any alphabets.
2. In the above image, you can see that unable to find categories. so when you are representing the demo so there should have at least one or two examples to find brands or categories.

Steps to reproduce

No response

Relevant log output

No response

Package

filament/filament

Package Version

have no idea

Laravel Version

have no idea

Livewire Version

have no idea

PHP Version

have no idea

Bug description

As you can see in the above image the date of birth calendar allows us to select future dates right? it should not be allowed to us. it should be disabled in the calendar.

Steps to reproduce

No response

Relevant log output

No response

error in php artisan migrate:refresh

public function down() { Schema::dropIfExists('shop_order_addresses'); }

instead of public function down() { Schema::dropIfExists('addresses'); }

DB_CONNECTION=mysql

New Fresh MySQL Database Coming migration already exists.

$ php artisan migrate:refresh

   INFO  Preparing database.

  Creating migration table ............................................................................................................... 12ms FAIL

   Illuminate\Database\QueryException 

  SQLSTATE[42S01]: Base table or view already exists: 1050 Table '`filament`.`migrations`' already exists (SQL: create table `migrations` (`id` int unsigned not null auto_increment primary key, `migration` varchar(255) not null, `batch` int not null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')      

  at C:\xampp\htdocs\root\prod\filament-demo\vendor\laravel\framework\src\Illuminate\Database\Connection.php:759
    755▕         // If an exception occurs when attempting to run a query, we'll format the error
    756▕         // message to include the bindings with SQL, which will make this exception a
    757▕         // lot more helpful to the developer instead of just the database's errors.
    758▕         catch (Exception $e) {
  ➜ 759▕             throw new QueryException(
    760▕                 $query, $this->prepareBindings($bindings), $e
    761▕             );
    762▕         }
    763▕     }

  1   C:\xampp\htdocs\root\prod\filament-demo\vendor\laravel\framework\src\Illuminate\Database\Connection.php:544
      PDOException::("SQLSTATE[42S01]: Base table or view already exists: 1050 Table '`filament`.`migrations`' already exists")

  2   C:\xampp\htdocs\root\prod\filament-demo\vendor\laravel\framework\src\Illuminate\Database\Connection.php:544
      PDOStatement::execute()

Hi there, On product edit page. after I uploaded image when I click save the image is gone (only show file name not image). What I'm missing? Thanks Panya

Just wanted to let ya'll know that when using mySQL instead of sqlite there is an error after running "php artisan db:seed" for this.. It works when I set config/database mysql strict=false, but otherwise it won't work. Don't know if you want to fix that or just tell the users who use mySQL instead to set that in config/database.. might lead to incorrect formats though when doing that. Also it's impossible to use this unless you enable pdo_sqlite extension in php.ini, some people who don't want to use sqlite and instead use mysql will have an error whenever they want to use the "composer install, composer require, or composer update" command... unless they want to use "--ignore-platform-req=ext-pdo_sqlite" at the end of every single composer command. Might want to let those people know this as well.