-
Notifications
You must be signed in to change notification settings - Fork 426
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(structure): History UI updates #7462
base: next
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Nov 7, 2024 5:35 PM (UTC) ❌ Failed Tests (1) -- expand for details
|
4b07286
to
39792f5
Compare
39792f5
to
17e81d0
Compare
* feat(sanity): update restore button * chore(sanity): update translations * feat(sanity): add left side information on footer (revision status line)
…el (#7435) * feat(structure): add history and review tabs to changes inspector panel * fix(structure): move changes inspector navigation to paneRouter * fix(structure): update isReviewChangesOpen check in ChangeConnectorRoot * fix(structure): rename uses of version to revision * chore(core): rename review changes action to history
…nks (#7449) * feat(structure): update TimelineItem to match new UI, prepare for chunks * chore(core): export getCalendarLabels to support DateTimeInput reusability
* feat(structure): add squashed chunks to timeline * feat(structure): refactor expandable item, all items need to be rendered in the same virtual list * feat(structure): expand elements on menu click * chore(structure): clean timeline item
2e16919
to
eaff9b0
Compare
@@ -194,7 +194,6 @@ export function useTimelineStore({ | |||
findRangeForSince: (chunk: Chunk) => controller.findRangeForNewSince(chunk), | |||
loadMore: () => { | |||
controller.setLoadMore(true) | |||
timelineStateRef.current.isLoading = true |
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 noticed this in some cases was blocking the ui in a loading state, which never ended because the load more action was not actually fetching new data, so the controller was not triggering any update, so the isLoading
returned in line 220 was never resetting to false.
if (didPublish) { | ||
if (changesOpen) { | ||
// Re-open the panel | ||
onHistoryOpen() | ||
} | ||
} |
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.
This is not necessary, the history panel won't close when a publish action happens.
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.
This is clean Pedro, fantastic job! ✨
Description
This PR introduces UI changes into the
history
andrevision
panel.What does "chunks are squashed together on publish" means?
Once the draft changes are published all the draft edits done before that publish will be squashed and shown as 1 change, that could be expanded, showing also the collaborators for that published.
This means:
If we have the following mutations:
[draftEdit, publish, draftEdit, draftEdit, create]
it will be shown as
[draftEdit, publish (expandable), create]
On expand, it will show the two collapsed draftEdit actions
The changes are not removed from the history, they are only visually squashed for easier navigation in the UI.
This is achieved by creating a relation between parents publish action and children draftEdit actions, in the addChunksMetadata function.
Collapsable.history.items.mov
What to review
Are the changes correct? Is something missing?
Testing
Notes for release
Updates to history inspector UI