jaymeh / laravel-publishable Goto Github PK

Add some improved documentation to the readme to talk about Laravel 9 support and which version to use.

The trait provided in this module relies heavily on adding a new published_at field to migrations and any model that uses it. Therefore it would make sense in the initialise hook that laravel can use to add the published_at field to a list of fillable properties.

It seems that the Orchestral Database package is no longer maintained, I've had some experience with Orchestral Testbench in the past but not sure what the difference is.

Ideally I would like to find an alternative to this and upgrade the test suite to utilise it.

I've got a project which relies on Events and triggering publish functionality seems to cause an issue with duplicate events firing. For that some new publishQuietly and unpublishQuietly functions would be pretty useful.

Hi,

I'm interesting in this package to provide functionality for making some models publishable. Just wondering if there are any plans to add Laravel 9 support in a new version? Laravel 9 requires PHP > 8.0 so may hinder any backwards compatability.

Happy to submit a PR with dependency bumps to make this happen but I wanted to check the project scope before putting the work in.

Cheers!

Laravel 10 is due to be released very soon (potentially next week). This package needs to be updated in order to allow compatibility.

I've been thinking about a recent change to include published_at as a fillable field but I'm wondering if the best solution for security would be to only update that attribute and recall save functions.

Some things to ponder:

• Overall security
• Model events (do they fire?)
• How do other packages handle this type of functionality?

The preset is currently setup to use one that doesn't quite fit our workflow. This will need to be updated to something like the "standard-changelog" preset.

This module currently assumes that you will always be using a published_at field on resources.

We should expose some configuration within this module which will allow you to change it to any field.

Implement conventional commits and conventional changelog functionality within this repository.

https://github.com/marcocesarato/php-conventional-changelog

Create a github action to ensure that all commits conform to conventional commits workflow.

I've added a PHP Library for creating a conventional changelog, I now just need to add a new action to create it.

Would be good to setup and run the tests through github actions.

Need to bump the version of checkout code action in CI from v2 to v3.

Create a factory macro which will allow you to seed a publishable field in some way.

Have you thought about adding a published_till variant as well.

You could schedule a model to be visible only during those two dates and after consider it an "archive"?

When running a migration, rather than specifically adding a field, it might be nice to have a publishable() migration helper function that allows content to apply the field much more easily. This may also make it much better when introducing new potential fields in later migrations if required.