You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We expect a version with title = Existing Title and optionally another version with title = New Title which matches the state of original/source Model.
Actual behaviour:
We are losing a version where title = Existing Title.
Possible Solution
It should create an initial version of the model first and then start saving the new versions.
Work around
I have a single Model called Post which uses the Versionable trait. So I created a console command SetupVersionable to create the initial versions of the Post model, before writers/users start changing the content.
Thanks for amazing work on this really hand package ❤️
I found an issue with version keeping, so here is an explaination.
Problem
When saving a Model for first time, It does not save the existing state of the model, instead it starts saving the new state of the model.
Steps to reproduce
Assuming, we have a Model with existing data:
Update the title of model
Expected behaviour:
We expect a version with
title = Existing Title
and optionally another version withtitle = New Title
which matches the state of original/source Model.Actual behaviour:
We are losing a version where
title = Existing Title
.Possible Solution
It should create an initial version of the model first and then start saving the new versions.
Work around
I have a single Model called Post which uses the Versionable trait. So I created a console command
SetupVersionable
to create the initial versions of the Post model, before writers/users start changing the content.The text was updated successfully, but these errors were encountered: