Optionally create initial version of model

[mansoorkhan96]

This pull request adds support for optionally creating a version for the initial/existing state of the model.

It fixes the issue: #51

[mansoorkhan96]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.

The reason for adding this option was this issue:
If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.

Here is a screenshot from a plugin i am currently working on.

[overtrue]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.

The reason for adding this option was this issue: If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.

Here is a screenshot from a plugin i am currently working on.

https://github.com/overtrue/laravel-versionable?tab=readme-ov-file#custom-version-store-strategy Does this fulfill your needs?

[mansoorkhan96]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.
The reason for adding this option was this issue: If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.
Here is a screenshot from a plugin i am currently working on.

https://github.com/overtrue/laravel-versionable?tab=readme-ov-file#custom-version-store-strategy Does this fulfill your needs?

Ah sounds like that would do it.
Let me try.

[mansoorkhan96]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.
The reason for adding this option was this issue: If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.
Here is a screenshot from a plugin i am currently working on.

https://github.com/overtrue/laravel-versionable?tab=readme-ov-file#custom-version-store-strategy Does this fulfill your needs?

Yes, changing Version Strategy already does that.
We can discard the last commit.

Thanks for time :)

[overtrue]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.
The reason for adding this option was this issue: If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.
Here is a screenshot from a plugin i am currently working on.

https://github.com/overtrue/laravel-versionable?tab=readme-ov-file#custom-version-store-strategy Does this fulfill your needs?

Yes, changing Version Strategy already does that. We can discard the last commit.

Thanks for time :)

Good!

[mansoorkhan96]

Should i push a commit by removing last commit changes?

[overtrue]

Should i push a commit by removing last commit changes?

Yes, please. thanks.

[mansoorkhan96]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.
The reason for adding this option was this issue: If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.
Here is a screenshot from a plugin i am currently working on.

https://github.com/overtrue/laravel-versionable?tab=readme-ov-file#custom-version-store-strategy Does this fulfill your needs?

Just realised the Snapshot version strategy saves all the model attributes instead of saving on the ones specified using: protected $versionable = ['title', 'content'];

[mansoorkhan96]

@overtrue I have added another commit. It adds a new config record_only_changed_attributes, true by default, which allows to optionally disable it and record all the attributes.
The reason for adding this option was this issue: If you dont change certain attributes, the diff starts becoming inconsistent by adding null to the diff.
Here is a screenshot from a plugin i am currently working on.

https://github.com/overtrue/laravel-versionable?tab=readme-ov-file#custom-version-store-strategy Does this fulfill your needs?

Just realised the Snapshot version strategy saves all the model attributes instead of saving on the ones specified using: protected $versionable = ['title', 'content'];

I think this is because of $this->getAttributes() in following code?

if ($this->getVersionStrategy() === VersionStrategy::SNAPSHOT && (! empty($changes) || ! empty($attributes))) {
    $changedKeys = array_keys($this->getAttributes());
}

It should be $changedKeys = array_keys($this->getVersionable());

Or we can even add a completely new strategy to do that?