This should (at least) be possible in the context of creating a new record.

Should probably support:

• default key
• that may optionally be a callable or even a class alias (that should implement an interface)
• otherwise, if scalar/literal, should be taken literally if the value is empty when creating a model

There seems to be a problem with the datepicker plugin, which causes the year mode to work inconsistently. After opening correctly once, it falls back to day-mode.

A work-around should be implemented for this.

PHP 7.2 changed count() to throw an E_WARNING when attempting to count non-countable types (this includes the sizeof() alias function).

PHP RFC: Counting of non-countable objects

Migrating from PHP 7.1.x to PHP 7.2.x

I suggest adding some sort of helper function to check if a variable contains a countable object before
counting it, something like this:

function is_countable ($value) {
    return is_array($value) || $value instanceof Countable;
}

Where should this function be placed?

It should be easy to add a simple boolean toggle to a model listing.

• The DefaultModelController should support this (with all the usual security checks).
• A ListColumn display strategy should be included for this.

This should function similarly to the column activate toggle.

Right now it is only possible to give a single column source reference for ListColumn strategies.

If comma-separated sources could be listed, this would allow for more flexibility in writing custom strategies.

Maybe this should be standardised for all sourced strategies.

The validation key of the options for a form field are only used with the file uploader module; they should also be applied while uploading directly.

Starting with Laravel 5.4, foreign key fields for Eloquent relations are resolved by the related model's primary key name and table name. According to the Laravel upgrade guide:

If the foreign key is not explicitly specified when defining a relationship, Eloquent will now use the table name and primary key name for the related model to build the foreign key. For the vast majority of applications, this is not a change of behavior.

For example:

/**
 * @property int $id - The primary key of Project
 */
class Project extends Model
{
    // this model's table name would be 'projects', so any foreign key would be
    //  built as 'project_id' by default, starting from Laravel 5.4
}

This means that I should be able to name my relation methods anything I see fit to provide some semantics, such as in the example below, where the relation method points to a certain Employee's favorite Project:

// Some other model that 'belongsTo' project...

class Employee extends Model
{
    /**
     * @return \Illuminate\Database\Eloquent\Relations\BelongsTo
     */
    public function favoriteProject()
    {
        return $this->belongsTo(Project::class);
    }
}

Within Laravel itself everything works as expected, but when I try to load the above model in the CMS, I get the following error:

Issue analysing model App\Models\Employee:

Foreign key ‘favorite_project_id’ defined for relation does not exist on model App\Models\Employee

Am I missing some configuration step? The workaround I have for now is just explicitly specifying the foreign key name in the belongsTo call, but I'd prefer to be able to omit that second argument:

return $this->belongsTo(Project::class, 'project_id');

Relevant info from my composer.json file:

{
    "require": {
        "czim/laravel-cms-acl-module": "0.9.3",
        "czim/laravel-cms-auth": "1.4.2",
        "czim/laravel-cms-core": "1.4.6",
        "czim/laravel-cms-models": "1.4.4",
        "czim/laravel-cms-theme": "0.9.8",
        "czim/laravel-cms-upload-module": "1.0.2",
    }
}

There seems to be a problem with Select2 that causes this.

A work-around should be made for this so AJAX relation lookups keep working.

For example, i've added a 'active' scope which filters the records bases on an active column boolean.

This gives me 2 tabs above the model list view, "All" and "Active". Now I wish to have "Active" selected as the default scope for my model.

The default cms-models config file should contain the PasswordUpdate strategy as a reference.

It's still pretty unclear from the documentation how List Parent setups can be made.

The default_top_relation comment is incomplete (dangling comma).

It would also help to add an example where the relation is between two separate models (f.i. a HasMany between a product and its variants).

When using the enum value \Czim\CmsModels\Support\Enums\FormDisplayStrategy::PASSWORD for a form display strategy, this refers to the DefaultStrategy, but without setting the type. Unless options.type is set to password, this causes unexpected behavior (a normal text input, instead of a password field).

Eloquent models may have their own connection defined.
For consistency, this connection should be used when making changes to the model through the CMS, unless specifically configured otherwise.