Skip to content
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: releases overview shows total docs in release #8232

Merged
merged 8 commits into from
Jan 16, 2025

Conversation

jordanl17
Copy link
Member

@jordanl17 jordanl17 commented Jan 10, 2025

Description

Scenario Before After
Active releases Screenshot 2025-01-10 at 16 03 46 Screenshot 2025-01-10 at 16 02 31
Archived/Published releases Screenshot 2025-01-10 at 16 04 20 Screenshot 2025-01-10 at 16 03 08
  • Split out the cell components for ReleasesOverview into separate components rather than all inside the column defs
  • Added tests for these cell components
  • Updated the cell component for the document count (ReleaseDocumentsCount), to:
    • use the documentsMetadata count for active releases
    • use the finalDocumentStates count for published or archived releases
  • Removed existingDocumentCount from the release metadata aggregator store as it's no longer needed

What to review

Testing

Added tests to the cell components

Notes for release

N/A

Copy link

vercel bot commented Jan 10, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
page-building-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 16, 2025 2:10pm
performance-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 16, 2025 2:10pm
test-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 16, 2025 2:10pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
studio-workshop ⬜️ Ignored (Inspect) Visit Preview Jan 16, 2025 2:10pm
test-next-studio ⬜️ Ignored (Inspect) Jan 16, 2025 2:10pm

Copy link
Contributor

No changes to documentation

Copy link
Contributor

github-actions bot commented Jan 10, 2025

Component Testing Report Updated Jan 16, 2025 2:10 PM (UTC)

❌ Failed Tests (1) -- expand for details
File Status Duration Passed Skipped Failed
comments/CommentInput.spec.tsx ✅ Passed (Inspect) 1m 4s 15 0 0
formBuilder/ArrayInput.spec.tsx ✅ Passed (Inspect) 12s 3 0 0
formBuilder/inputs/PortableText/Annotations.spec.tsx ❌ Failed (Inspect) 1m 18s 5 0 1
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx ✅ Passed (Inspect) 51s 11 7 0
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx ✅ Passed (Inspect) 0s 0 12 0
formBuilder/inputs/PortableText/Decorators.spec.tsx ✅ Passed (Inspect) 26s 6 0 0
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx ✅ Passed (Inspect) 14s 3 0 0
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx ✅ Passed (Inspect) 26s 6 0 0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx ✅ Passed (Inspect) 1m 6s 15 0 0
formBuilder/inputs/PortableText/Input.spec.tsx ✅ Passed (Inspect) 1m 28s 21 0 0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx ✅ Passed (Inspect) 1m 41s 18 0 0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx ✅ Passed (Inspect) 13s 3 9 0
formBuilder/inputs/PortableText/Styles.spec.tsx ✅ Passed (Inspect) 26s 6 0 0
formBuilder/inputs/PortableText/Toolbar.spec.tsx ✅ Passed (Inspect) 1m 43s 21 0 0
formBuilder/tree-editing/TreeEditing.spec.tsx ✅ Passed (Inspect) 0s 0 3 0
formBuilder/tree-editing/TreeEditingNestedObjects.spec.tsx ✅ Passed (Inspect) 0s 0 3 0

Copy link
Contributor

github-actions bot commented Jan 10, 2025

⚡️ Editor Performance Report

Updated Thu, 16 Jan 2025 14:11:27 GMT

Benchmark reference
latency of sanity@latest
experiment
latency of this branch
Δ (%)
latency difference
article (title) 25.3 efps (40ms) 27.8 efps (36ms) -4ms (-8.9%)
article (body) 67.8 efps (15ms) 63.3 efps (16ms) +1ms (-/-%)
article (string inside object) 25.6 efps (39ms) 29.4 efps (34ms) -5ms (-12.8%)
article (string inside array) 25.3 efps (40ms) 25.0 efps (40ms) +1ms (+1.3%)
recipe (name) 47.6 efps (21ms) 62.5 efps (16ms) -5ms (-23.8%)
recipe (description) 55.6 efps (18ms) 62.5 efps (16ms) -2ms (-11.1%)
recipe (instructions) 99.9+ efps (5ms) 99.9+ efps (5ms) +0ms (-/-%)
synthetic (title) 19.2 efps (52ms) 21.3 efps (47ms) -5ms (-9.6%)
synthetic (string inside object) 18.9 efps (53ms) 19.8 efps (51ms) -3ms (-4.7%)

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark latency p75 p90 p99 blocking time test duration
article (title) 40ms 51ms 71ms 520ms 916ms 10.9s
article (body) 15ms 16ms 20ms 188ms 202ms 5.4s
article (string inside object) 39ms 42ms 45ms 136ms 177ms 6.7s
article (string inside array) 40ms 42ms 48ms 174ms 150ms 6.7s
recipe (name) 21ms 24ms 28ms 47ms 0ms 7.0s
recipe (description) 18ms 19ms 21ms 39ms 0ms 4.6s
recipe (instructions) 5ms 7ms 8ms 19ms 0ms 3.0s
synthetic (title) 52ms 54ms 58ms 97ms 488ms 12.3s
synthetic (string inside object) 53ms 55ms 64ms 459ms 1176ms 8.6s

🧪 Experiment result

The performance result of this branch

Benchmark latency p75 p90 p99 blocking time test duration
article (title) 36ms 45ms 65ms 498ms 828ms 10.6s
article (body) 16ms 19ms 27ms 169ms 238ms 5.4s
article (string inside object) 34ms 37ms 40ms 177ms 171ms 7.1s
article (string inside array) 40ms 43ms 48ms 174ms 185ms 6.8s
recipe (name) 16ms 19ms 21ms 37ms 0ms 6.7s
recipe (description) 16ms 17ms 20ms 36ms 0ms 4.5s
recipe (instructions) 5ms 7ms 7ms 10ms 0ms 3.1s
synthetic (title) 47ms 48ms 52ms 81ms 317ms 12.8s
synthetic (string inside object) 51ms 53ms 64ms 400ms 1302ms 8.9s

📚 Glossary

column definitions

  • benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
  • latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
  • p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
  • p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
  • p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
  • blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
  • test duration — how long the test run took to complete.

@jordanl17 jordanl17 force-pushed the corel-292-total-overview-count branch from aac22cd to b8f3e20 Compare January 10, 2025 10:46
@jordanl17 jordanl17 marked this pull request as ready for review January 10, 2025 16:19
@jordanl17 jordanl17 requested a review from a team as a code owner January 10, 2025 16:19
@jordanl17 jordanl17 requested review from rexxars, bjoerge, RitaDias and pedrobonamin and removed request for a team, rexxars, bjoerge and RitaDias January 10, 2025 16:19
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test change isn't entirely relevant to the task at hand, but I came across it and thought it would be good to try and move as quickly as possible to using the release fixtures everywhere

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing existingDocumentsCount from the store record

@jordanl17 jordanl17 requested a review from juice49 January 14, 2025 13:30
return (
<Translate
t={t}
i18nKey={documentCount > 1 ? `document-count_other` : `document-count_one`}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

our i18n tool actually handles these causes automatically, as far as I know you shouldn't need to do this :)
You need to send in the count like this (example on our code base, translation with count, use in component)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh well that's quite nice! There are a few other places I've done this (the wrong) thing. I'll remember to go back and update them.

Thanks for flagging. However clever of them!

Copy link
Contributor

@RitaDias RitaDias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great to me!
I guess the only thing would be about the translation key but otherwise everything looks good to go. My question is: are we going to add the separation of document changes (added, modified, deleted etc) at a later point or is that something that was dropped for now?

@RitaDias
Copy link
Contributor

Also, from a design stand point I really don't like how the numbers and text split the line, do we have to have the "documents" text there? :( Can't we add the header with the information that we are showing the count?

image

@jordanl17
Copy link
Member Author

This looks great to me! I guess the only thing would be about the translation key but otherwise everything looks good to go. My question is: are we going to add the separation of document changes (added, modified, deleted etc) at a later point or is that something that was dropped for now?

That's been dropped now. The document action will only be present on release dashboard lists, but since this requires some backend work in places to make performant, we aren't going to touch it until a later date.

@jordanl17
Copy link
Member Author

Also, from a design stand point I really don't like how the numbers and text split the line, do we have to have the "documents" text there? :( Can't we add the header with the information that we are showing the count?

image

Valid concern. I've sort of designed this interpolating between a few different versions of prototype we've had. I'll note for Marius to look over this retrospectively

@jordanl17 jordanl17 requested a review from RitaDias January 16, 2025 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants