-
Notifications
You must be signed in to change notification settings - Fork 46
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
Component Explorer Improvements + Speed Boost #1013
Conversation
…ountered with older buggy versions of lit-html directives
…er intro section for the component explorer UI; add pre-rendered HTML to help with initial page loading experience
… viewer accordion
…component + schema form sub-component; addresses performance and re-rendering issues encountered when only using Preact for handling the overall component rendering
⚡ PR built on Travis and deployed a now preview here:
|
…wo lines on the smallest screen sizes
Performance Test Comparing These Updates: Mobile: https://www.webpagetest.org/video/view.php?id=190107_156243b594a2bb3ee6eb96e06f289205ef33126c Desktop: https://www.webpagetest.org/video/view.php?id=190107_a42574deca0bd85d648e62002cbb18acb983a3be |
⚡ PR built on Travis and deployed a now preview here:
|
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.
Tested button
and navbar
, worked as expected and noticeably snappier 👍
As discussed, it is not rendering in IE, but same is true on master so this is not a regression. Layout issues with IE have been fixed, too.
Jira
http://vjira2:8080/browse/BDS-879?filter=-1
Summary
UI cleanup + overall improvements to the new component explorer component on the boltdesignsystem.com site.
Details
These updates should help speed up the initial and subsequent component being rendered + improves the accuracy of the component re-renders (via splitting apart the React JSON Schema Form UI into a Preact-specific component and decoupling this from the rendered component via Lit-HTML...)
Funny enough, no longer rendering this component preview in an iFrame helps a TON with the overall performance of this!
How to test