feat(history): add history-version content type #19316
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remidej
added
source: core:content-manager
Marc-Roig
reviewed
Jan 25, 2024
packages/core/content-manager/server/src/history/content-types/history-version.ts
Outdated
Show resolved
Hide resolved
Marc-Roig
reviewed
Jan 25, 2024
packages/core/content-manager/server/src/history/content-types/history-version.ts
Outdated
Show resolved
Hide resolved
Marc-Roig
reviewed
Jan 25, 2024
packages/core/content-manager/server/src/history/content-types/history-version.ts
Show resolved
Hide resolved
markkaylor
reviewed
Jan 25, 2024
markkaylor
reviewed
Jan 25, 2024
packages/core/content-manager/server/src/history/content-types/history-version.ts
Outdated
Show resolved
Hide resolved
Marc-Roig
approved these changes
Jan 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
Registers a history version content type. It's a content type for now, but it will converted to a model later when Alex finished his database model API proposal.
I had to add a few unusual fields (modelName, globalId) because they were mandatory in the type. I checked against all the other content types at runtime to make sure I matched the right format.
Why is it needed?
To later store content history data
How to test it?
yarn strapi consolestrapi.contentTypes['plugin::content-manager.history-version']