Its always failing to install. After a search I have deleted the Vendor folder, composer.lock but still no luck. I have logviewer and noCaptcha on my system:

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Can only install one of: arcanedev/support[4.4.0, 4.3.0].
- Can only install one of: arcanedev/support[4.4.0, 4.3.0].
- Can only install one of: arcanedev/support[4.4.0, 4.3.0].
- arcanedev/laravel-notes 4.0.0 requires arcanedev/support ~4.4.0 -> satisfiable by arcanedev/support[4.4.0].
- Installation request for arcanedev/laravel-notes ^4.0 -> satisfiable by arcanedev/laravel-notes[4.0.0].
- Installation request for arcanedev/support (locked at 4.3.0) -> satisfiable by arcanedev/support[4.3.0].

Any chance of getting this up/running with Laravel 7...? :-)

Given the ability to publish migrations #16, it would be desirable to be able to incorporate outside libraries with this one, such as the Userstamps library found here.

This would mean making author_id configurable as a column name.

Hello,

Is it possible to add a constraint to the $post->notes to allow them to be displayed in date descending order?

Thanks

Please, would be great to have:

php artisan vendor:publish --provider="Arcanedev\LaravelNotes\LaravelNotesServiceProvider" --tag=migrations

Thank you anyway!

Right now the cascade is setup if a user is deleted. However, if I delete my model entry (the noteable) it should also delete the note.

I deleted to test, and now I have an orphaned note.

https://github.com/ARCANEDEV/LaravelNotes/blob/master/database/migrations/2016_10_00_000001_create_notes_table.php#L47

User deletions are correct, but the noteable itself doesn't delete the note if I delete the noteable.

For new laravel installs, there will be two issues.

1. There is inconsistency with the default laravel migrations & the migrations used here.

2. The author_id foreign key will not work as it uses unsignedInteger however for laravel 5.8 the users id column is bigIncrements.

laravel/laravel@426df7a

Upgrading to Laravel 9, the version 8.1 does not work anymore

Your requirements could not be resolved to an installable set of packages.

Problem 1
- arcanedev/support 8.0.0 requires laravel/framework ^8.0 -> found laravel/framework[v8.0.0, ..., 8.x-dev] but it conflicts with your root composer.json require (^9.0).
- arcanedev/support 8.0.1 requires php ^7.3 -> your php version (8.1.1) does not satisfy that requirement.
- illuminate/contracts[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.1.1) does not satisfy that requirement.
- Only one of these can be installed: illuminate/contracts[dev-master, v5.0.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev], laravel/framework[v9.0.0-beta.1, ..., 9.x-dev]. laravel/framework replaces illuminate/contracts and thus cannot coexist with it.
- arcanedev/support 8.1.0 requires illuminate/contracts ^8.0 -> satisfiable by illuminate/contracts[v8.0.0, ..., 8.x-dev].
- arcanedev/laravel-notes 8.1.0 requires arcanedev/support ^8.0 -> satisfiable by arcanedev/support[8.0.0, 8.0.1, 8.1.0].
- Root composer.json requires arcanedev/laravel-notes ^8.1 -> satisfiable by arcanedev/laravel-notes[8.1.0].
- Root composer.json requires laravel/framework ^9.0 -> satisfiable by laravel/framework[v9.0.0-beta.1, ..., 9.x-dev].

The package claims to have support for lower versions of Laravel than 5.4, but depends on the arcanedev/support v4.0.0 package, which itself depends on illuminate/support v5.4.0.

Running into lint issues that properties dont exist on the Note model because the @property declarations in src/Model/Note is missing the $ prefix for the proeprty names

Be great is this project fixed that so I (and possibly many others) don't have to manually add it - in my case, i'm using ecs to lint the project, that picks up class properties from migrations, but if there isn't a migration, it will use docblocks

Will open a pr soon and see if you want agree or not

This package uses automatic migration discovery, but this has two drawbacks.

1. It will only work if you run php artisan migrate without any parameters, if you run something like php artisan migrate --path="some/path" it will not run the package migration.
2. It is not possible to modify the notes table.

Sometimes you need to specify the migration path, or make some modifications to the notes table so I think is better to publish the migration file the same way the config file is published.

I have updated the notes.php to this:

'authors' => [
        'table' => 'users',
        'model' => App\Models\User::class,
    ],

But it's not working, I already tried doing php artisan config:clear and php artisan config:cache and composer dump-autoload

Attempting to install LaravelNotes on a homestead installation. Already have arcanedev/laravel-settings installed.

Using version ^3.0 for arcanedev/laravel-notes
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Can only install one of: arcanedev/support[4.3.0, 4.2.2].
    - Can only install one of: arcanedev/support[4.3.0, 4.2.2].
    - Can only install one of: arcanedev/support[4.3.0, 4.2.2].
    - arcanedev/laravel-notes 3.0.0 requires arcanedev/support ~4.3.0 -> satisfiable by arcanedev/support[4.3.0].
    - Installation request for arcanedev/laravel-notes ^3.0 -> satisfiable by arcanedev/laravel-notes[3.0.0].
    - Installation request for arcanedev/support (locked at 4.2.2) -> satisfiable by arcanedev/support[4.2.2].


Installation failed, reverting ./composer.json to its original content.