feat: allow editors to summarise operations in "History" timeline #4283
+506
−264
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.
A small indepedent feature that we need to support both templates and publishing tickets in this SOW (similar to flows being published & offline by default) is the ability for editors to insert "comments" into the current "History" timeline.
The "History" timeline currently reads from
operations
and displays a human translation of the JSON OT. Operations will remain the only timeline items that can be "restored", but the "comments" will allow editors to insert notes which essentially act like subheaders on the timeline between groups of operations to contextualise the bigger picture (eg "Implemented new CIL Form 1") between publishes (which may still include 1,000s of individual node operations).These will enable us to show more friendly change logs on publish as well as help templated flow users understand how the source template content has been changing.
It's in our interest to introduce this feature early, not under the "TEMPLATES" feature flag, so that editors can actually start using it in the meantime even though we are not adjusting the "Check for changes to publish" dialog just yet.
Todo:
flow_change_logs
teamEditors
to insert comments about their flows_stream
query option in Hasura? (If a view-based approach, should we join published flows too?)