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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: undo operations to a flow #3056
feat: undo operations to a flow #3056
Changes from 1 commit
f06f3bd
2faeb09
bcb7a4e
5c021b1
3575fec
1a6d80b
6503713
750d73e
adca0b0
90c1aff
c737103
f86d0c9
2d948fd
53009bf
b7f0bad
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered LOTS of different ways of doing this piece - but eventually landed on this simple Editor store method which hooks into our existing
send(ops)
- meaning we don't have to directly write any mutations to updateoperations
orflows
as the original script does: https://github.com/theopensystemslab/planx-data-recovery/blob/main/index.jsThe other main route I was considering was creating an API endpoint to mimic the full set of data-recovery steps (eg
/flows/:flowId/undo/:operationId
). Ultimately decided against this though in favor of an Editor-only approach for a couple key reasons:version
aligned - and flow version is something that we rarely manually deal with in flow data clients etc. Again, hooking into existing Editor methods means we're just getting that alignment "for free" (similar for user/actor id doing the "undo"!)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super helpful explanation here thanks.