[WIP] History UI #4398
Closed
[WIP] History UI #4398
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
|
Good feature to have. Please merge at the earliest. |
|
Did this ever get into beta-7 or -8 ? |
|
It's this feature added in keystone master? |
|
Anyway to get this into the build? I think it is failing due to missing tests. |
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.
Description of changes
Introduces a History button for models who have
history: true. This allows a user to track historical revisions and revert an instance if necessary.This was an immediate need of a client and I am publishing this code here for anybody who may find it useful.
Related issues (if any)
#2212, #1241, etc.
Testing
npm run test-allran successfully.