v1.0 #2233
Open
v1.0 #2233
+31,700
−31,776
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: de5b868 The changes in this PR will be included in the next version bump. This PR includes changesets to release 73 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@segunadebayo will this negate this issue - #2232 ? I see the deep-merge function is being removed in this PR |
|
@veloware Yes, it will. We're simplifying pretty much everything |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #2226
Closes #2214
Closes #2179
Closes #2238
Closes #2223
Closes #2235
Closes #2252
Closes #2213
📝 Description
Over the years, we've nailed down the correct Zag APIs that work across frameworks. We're shifting focus to runtime and rendering performance to make it blazing fast.
Based on preliminary measurements of testing 10k instances of the same components.
The results show roughly 1.5x - 4x performance improvements across components. Here are the results
Avatar
Before
{phase: 'mount', duration: 1007.3000000119209} {phase: 'update', duration: 890.4000000357628}After
{phase: 'mount', duration: 736.9999999403954} {phase: 'update', duration: 1.899999976158142}Accordion
Before
{phase: 'mount', duration: 2778.4999997913837} {phase: 'update', duration: 2.3000000715255737}After
{phase: 'mount', duration: 1079.0000001490116}Collapsible
Before
{phase: 'mount', duration: 834.4000000357628} {phase: 'update', duration: 2.1999999284744263}After
{phase: 'mount', duration: 290.3000001013279}Dialog
Before
{phase: 'mount', duration: 688.9000000357628} {phase: 'update', duration: 2.0000000298023224}After
{phase: 'mount', duration: 135.50000008940697}Editable
Before
{phase: 'mount', duration: 1679.500000089407} {phase: 'update', duration: 2.0000000298023224}After
{phase: 'mount', duration: 737.5999999940395}Tooltip
Before
{phase: 'mount', duration: 797.7999999821186} {phase: 'update', duration: 2.5999999940395355}After
{phase: 'mount', duration: 139.9000000357628}Presence
Before
{ phase: "mount", duration: 1414 } { phase: "update", duration: 0 }After
{ phase: "mount", duration: 502 }Tabs
Before
{ phase: "mount", duration: 4120 } { phase: "update", duration: 2014 }After
{ phase: "mount", duration: 3880 } { phase: "nested-update", duration: 3179 }💣 Is this a breaking change (Yes/No):
Just a slight change in syntax. Nothing major