* Not found property rule
* Make these “better”
* Day 1
* Day 2
* Day 3
* Dat 4
* Remove disabled check
* Day 4 continued
* Run pint
* Final changes hopefully
* Pint fixes
* Fix again
* Reset these
* Update app/Filament/Admin/Pages/Health.php
Co-authored-by: MartinOscar <40749467+rmartinoscar@users.noreply.github.com>
* Update app/Traits/CheckMigrationsTrait.php
Co-authored-by: MartinOscar <40749467+rmartinoscar@users.noreply.github.com>
---------
Co-authored-by: MartinOscar <40749467+rmartinoscar@users.noreply.github.com>
* Add php 8.4
* Update ide helper
* Add php 8.4
* Update laravel sanctum
* Update laravel framework
* Hash rounds were increased
* This is always false
* Extend model now
* This does nothing
* Move model validation methods to trait
* Remove base model
* Backup routes were previously referenced by uuids
* Remove commented code
* Upgrade laravel/framework
* Fix migration
* Update ide helper
* Update sanctum
* Add version to composer
* Add this back in, fixed
* Make this protected to be safer
* use RESOURCE_NAME for requests
* use RESOURCE_NAME for transformers
* add permissions field to api key
* add migration for new permissions field
* update tests
* remove debug log
* set column type to "json"
* remove default attribute to fix tests
* fix default value for permissions
* fix after merge
* fix after merge
* allow to "register" custom permissions
* add "role" to default resource names
* fix after merge
* fix phpstan
* fix migrations
* add application api endpoints for mounts
* run pint
* add mounts resource to api key
* add includes to mount transformer
* forgot delete route for mount itself
* add migration for "r_mounts" column
* add mounts to testcase api key
Drops all of the eloquence requirements, this is going to break a shit load of code, needs to happen tired of this package always holding us back.
Quite confident in my ability to write custom code to do the basic validation we need.
Searching should be a fun nightmare to deal with later...
Main difference is permissions, cleaner UI for normal users, and account keys use permissions assigned to servers and subusers while application keys use R/W ACLs stored in the key table.
