feat(history): restore version

[markkaylor]

What does it do?

• Adds the logic to a version
• Adds a simple dumb button on the FE + sets up the RTK mutation to make it easier to test

Why is it needed?

• To restore a history version

How to test it?

• Create a history version for an entry
• Create another with some changes
• Go to history and restore the previous version
• It should create a new history version that restore your selected version

Test relations and media

• Add relations/media to an entry, create a history version
• Go delete the relation/media entries/assets, create another history version for the entry
• Restore the version that had the relations/media
• The deleted relations should not be restored, existing relations should be restored

Unknown fields:

• Added fields should be in the restored version but with an empty value
• Deleted fields should not be restored

Not supported:

• polymorphic relations / components

NOTE

To ensure this work makes it into the beta blitz on monday tests will be handled in another PR CS-752

[Marc-Roig]

History has only a single service, which is now in charge of :

• Handling strapi lifecycles (bootstrap, destroy)
• version management (createVersion, findVersionsPage, restoreVersion)

Would it make sense to split the history service into two?

• lifecycles service exposing bootsrap() and destroy()
• history-versions service exposing create() findPage() restore()

It could simplify method naming and split the services concerns

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
contributor-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 16, 2024 7:03am

[Marc-Roig]

unrelated to this PR, but you might want to change the following line in the history service:

// before
const localesService = strapi.plugin('i18n').service('locales');

// after
const localesService = strapi.plugin('i18n')?.service('locales');

// Return or handle it differently
if  (!localesService) return

if i18n is not enabled that might break

[remidej]

I think we're ready to merge and treat potential issues as bug fixes PRs

[markkaylor]

@remidej I'll push to address Marc's feedback for:
Two services lifecycles and history reverted, let's do this in another PR

• Validate the request body

Then good to merge with follow up PRs for bug fixes + tests

[markkaylor]

@remidej and/or @Marc-Roig could you please test the validation of the request body and the validation of update permissions. For the update permissions here I am getting 403 when I don't the permissions.

[remidej]

Tested again ✅

[markkaylor]

The failing FE test is unrelated. Merging.