When I try to execute the command php artisan optimize in production environments, I get a logical exception because the configuration offered by this package is not serializable.

LogicException 

  Your configuration files are not serializable.

  at vendor/laravel/framework/src/Illuminate/Foundation/Console/ConfigCacheCommand.php:71
     67▕             require $configPath;
     68▕         } catch (Throwable $e) {
     69▕             $this->files->delete($configPath);
     70▕ 
  ➜  71▕             throw new LogicException('Your configuration files are not serializable.', 0, $e);
     72▕         }
     73▕ 
     74▕         $this->info('Configuration cached successfully!');
     75▕     }

  1   bootstrap/cache/config.php:781
      Error::("Call to undefined method App\Nebula\Resources\UserResource::__set_state()")

      +27 vendor frames 
  29  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

This is probably due to the fact that we store resource instances, dashboards, etc. in the configuration file. As a possible solution, we could give the user the option to assign namespaces as follows.

// config/nebula.php

return [
    'resources' => [
        UserResource::class,
    ],

    'dashboards' => [
       UserDashboard::class,
    ],
];

I could try to solve it, what do you think?

Refactor the make() method so it takes the label first and accepts a column:

Input::make('Name', 'column')

name is required and the column is optional

Fixes #32

I added the 4 route resolvers to the folder, as it was discussed in the issue; each one with a static method: bind

and the NebulaServiceProvider calls these methods in its boot method.

This PR enables users to build and register custom pages within the Nebula panel.

It introduces a new php artisan nebula:page command that will generate a new class in app/Nebula/Pages, as well as a view under resources/views/nebula/pages.

To register a new page, you follow the same pattern as the dashboards and resources, adding new PageClass under the nebula.pages configuration option.

The idea for these pages is similar to Laravel Nova's custom tools. Have a uniform API that allows developers to build third-party extensions for Nebula.

I've named them pages because using the term Tool felt too similar to Nova, but I'm happy to change this.

It's also worth noting that the developer doesn't need to use the nebula::layouts.shell view in their pages view, since it will automatically be wrapped in it. Instead, they only need to worry about what their page will display.

The page also moves away from the singularName() and pluralName() pattern that the resources & dashboards follow because it didn't make much sense here. Instead the NebulaPage::name() method will be used for displaying the menu item and the page title.

For the URL slug / route binding, a new NebulaPage::slug() method has been introduced which will be used to match the page.

Happy to hear thoughts and ideas on this - this was the simplest implementation after all. 🤗

Hi, all features is compatible with Laravel 8 ? I tried to create a new project, following all the steps in the documentation, but when the user's CRUD is accessed it returns the error:

and when I try to insert a new record:

Thanks in advance

Hi

Just tried to install Nebula using the the instructions: https://nebulapackage.com/installation

I then created a new 'UserResource' Registered the resource in the config file

http://test.test/nebula/resources/users

simply return 404

This PR adds a couple of new methods to the NebulaDashboard class:

• NebulaDashboard::display() - similar to NebulaPage::display(), is the parent method used for calling the underlying render method.

• NebulaDashboard::render() - used to change the view that a dashboard returns, allowing for custom views.

• NebulaDashboard::displayMetrics() - used to render the metrics, using the default view provided by Nebula.

These changes will allow developers to change the view that is used for the dashboard, greatly improving the customisation, whilst still being able to render the default metrics view.

This PR adds 6 new methods to a brand new Nebula class in the root of the package. This class will act as the central source of truth for resources, dashboards and now pages.

Nebula::resources() - used to register an array of resources:

Nebula::resources([
    ExampleResource::class,
]);

Nebula::availableResources() - used to retrieve the array of available / registered resources.

There are equivalent methods for dashboards and pages too. This will allow developers to manually register resources inside of a service providers boot method, and will also create a new place for more filtering based on permissions, etc in the future.

This PR provides option for overriding default views.

User will be able to publish the view files to resources/views/vendor/nebula and override them as they like.

I want to make some of my resources only viewable, but don't allow create, edit or delete them. So I need only basic index view. How can I achieve this?

Just got a BindingResolutionError because the PageController doesn't exist while it's being used in routes/web.php. I thought it was just an issue on my dev environment, but it doesn't seem to exist on the master branch either.

You have done a very good job.

There are errors in the documentation, for example, there is no class named InputField, it must be Input::make(). Also php artisan make:filter WhereNameStartsWithAFilter this command does not exist "Command 'make: filter' is not defined." it must be php artisan nebula:filter FilterName. Example in resources page.

[InvalidArgumentException]
Package larsklopstra/nebula has a PHP requirement incompatible with your PHP version, PHP extensions and Composer version

Suggestion:

"require": { "php": "^7.4|^8.0", ... }

How to append custom attributes to field? For example on User model, I have field first_name and last_name. And i make custom attribute called full_name

// App/Model/User.php
public function getFullNameAttribute(){
return $this->first_name.' '.$this->last_name;
}

I'm able to access the dashboard at /nebula with the NebulaEmailAuthStrategy enabled, while not being logged in at all (also tried this on incognito).

Surely this shouldn't be the case.