Closed str closed 1 year ago
Hey @str
When creating custom plugins you do not need to use override folders if you are using the make:plugin
command. The command will generate a PHP class that will handle your needs for routes, views, models, controllers, and such. Keep in mind the overrides folder is for site-wide settings and there can only be one config
, app
, and other folder pre-project.
I now better understand how things work...at least a bit. This error happens when you run galaxy
with PHP 8.1. This does not happen if you use PHP 8.0
Hey @str
TypeRocket does not yet have full support for PHP 8.1. However, we are working to be ready with PHP 8.1. There are several changes that need to be made for 8.1 to be fully supported and we also need some of the packages like Whoops PHP to gain support as well.
@kevindees Whoops was replaced by Laravel for ignition which is full PHP 8.1 compatible.
@str is there a none Laravel version? I have seen this but I'm not aware of a framework agnostic version.
@kevindees checking the github discussions, they asked how to integrate it in other frameworks: https://github.com/facade/ignition/discussions/459
@str
We have added much better support for PHP 8.0 and some for 8.1 in v6 of TypeRocket.
I wanted to
make:plugin
. Before making the plugin there was no $overrides folder, so I pointed both vars to the same typerocket folder. This ran fine, but after creating the plugin, the system crashed if I ran the galaxy command again.This is solved if I point
$overrides
to the plugin we created BUT it does not make sense if I want to have multiple typerocket-based plugins.