You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Add disable action when user doesn't have permission to discard version in document action and in the release detail table
Add disable action when user doesn't have permission to unpublish document in the release detail table
Update document action to new action
Permissions there now use the versions
Updated tooltip text for different conditions on the unpublish action
Screen.Recording.2025-02-12.at.09.45.20.mov
What to review
Does everything look alright?
Testing
Didn't add tests to the menu actions since the larger changes happened directly in the permission aspect of things
To manually test you should use a user that doesn't have permissions (viewer), the debug roles don't work consistently.
Notes for release
Document actions (discard version and unpublish) in a release now respect permissions
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)
39ms
41ms
46ms
104ms
69ms
11.4s
article (body)
14ms
16ms
18ms
114ms
88ms
5.1s
article (string inside object)
36ms
38ms
45ms
157ms
126ms
6.4s
article (string inside array)
42ms
45ms
51ms
153ms
332ms
7.3s
recipe (name)
20ms
21ms
24ms
48ms
4ms
7.2s
recipe (description)
17ms
18ms
20ms
30ms
0ms
4.5s
recipe (instructions)
5ms
7ms
8ms
9ms
0ms
3.1s
synthetic (title)
48ms
54ms
58ms
495ms
917ms
12.8s
synthetic (string inside object)
49ms
52ms
65ms
456ms
907ms
8.5s
🧪 Experiment result
The performance result of this branch
Benchmark
latency
p75
p90
p99
blocking time
test duration
article (title)
37ms
40ms
42ms
307ms
11ms
10.0s
article (body)
14ms
16ms
20ms
161ms
199ms
5.2s
article (string inside object)
37ms
40ms
45ms
171ms
349ms
7.1s
article (string inside array)
42ms
44ms
47ms
74ms
245ms
6.8s
recipe (name)
20ms
21ms
24ms
34ms
0ms
7.3s
recipe (description)
17ms
18ms
19ms
20ms
0ms
4.4s
recipe (instructions)
5ms
6ms
7ms
19ms
0ms
3.1s
synthetic (title)
49ms
51ms
54ms
68ms
267ms
12.1s
synthetic (string inside object)
48ms
49ms
50ms
54ms
210ms
7.1s
📚 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.
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
Screen.Recording.2025-02-12.at.09.45.20.mov
What to review
Does everything look alright?
Testing
Didn't add tests to the menu actions since the larger changes happened directly in the permission aspect of things
To manually test you should use a user that doesn't have permissions (viewer), the debug roles don't work consistently.
Notes for release
Document actions (discard version and unpublish) in a release now respect permissions