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
Open the version of a document when that version is the only one (no draft, no published)
In instances where multiple versions exist (but no draft and no published), then it will default to the first version
Fix issues around the disabling of the draft
Fix whitespace in add to release banner
Note
We don't want to set the pinned version to match the version because, imo, it makes sense to still have the version open when you press a different pinned version to add them to another release
What to review
Does it make sense? Is there a better way to go about it?
Testing
Updated tests, added new test
To test the provider would e a larger task which I think best left outside of the scope of this PR
Notes for release
When a document only has a version of itself, it will open that version instead of the draft
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)
37ms
41ms
57ms
398ms
634ms
9.8s
article (body)
15ms
18ms
26ms
132ms
197ms
5.8s
article (string inside object)
36ms
38ms
44ms
151ms
391ms
7.1s
article (string inside array)
41ms
44ms
50ms
75ms
350ms
7.0s
recipe (name)
22ms
24ms
27ms
44ms
0ms
7.2s
recipe (description)
19ms
20ms
22ms
53ms
0ms
4.9s
recipe (instructions)
5ms
7ms
7ms
29ms
0ms
3.1s
synthetic (title)
53ms
56ms
58ms
232ms
1006ms
26.8s
synthetic (string inside object)
53ms
57ms
70ms
390ms
1568ms
9.5s
🧪 Experiment result
The performance result of this branch
Benchmark
latency
p75
p90
p99
blocking time
test duration
article (title)
47ms
54ms
76ms
386ms
1122ms
11.9s
article (body)
14ms
17ms
31ms
184ms
558ms
5.9s
article (string inside object)
43ms
46ms
54ms
237ms
307ms
7.4s
article (string inside array)
48ms
50ms
61ms
170ms
613ms
8.0s
recipe (name)
21ms
22ms
24ms
41ms
0ms
7.0s
recipe (description)
18ms
19ms
20ms
39ms
0ms
4.6s
recipe (instructions)
6ms
7ms
9ms
25ms
0ms
3.2s
synthetic (title)
51ms
56ms
73ms
450ms
966ms
16.9s
synthetic (string inside object)
53ms
56ms
59ms
423ms
1053ms
8.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.
RitaDias
changed the title
fix(structure): navigate to version when no draft or published document
fix(structure): navigate to version when document only has versions
Feb 26, 2025
…a orphan version but no draft)
fix(structre): make sure that you get the first version of the document in case if there are no drafts or published when viewing a different release
fix(structure): fix issue when reading versins when they don't exist / drafts and published exist
fix(structure): fix issue where you couldn't remove the pinned version
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
Note
We don't want to set the pinned version to match the version because, imo, it makes sense to still have the version open when you press a different pinned version to add them to another release
What to review
Does it make sense? Is there a better way to go about it?
Testing
Updated tests, added new test
To test the provider would e a larger task which I think best left outside of the scope of this PR
Notes for release
When a document only has a version of itself, it will open that version instead of the draft