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 is probably best as a plugin rather than a feature request, but I think Elder's architecture lends itself to something I have yet to see automatic, perfectly sized skeletons.
What I notice in my own process is that I put dummy data in while styling dynamic components, then I wire up the dynamic portion. Invariably I discover a few places wherein a store or reactive element fails during the static build and some workaround is needed. Then the rendered page has some empty bits that are never seen when live but are visible when javascript is disabled.
There are many solutions to this, but I think we could turn it into a big positive by adding a hook that replaces dummy elements with skeleton replacements. This could be done in a way that doesn't add any additional overhead -- usually, this requires one to specify the rendered size (which is hard to get right).
Any thoughts?
The text was updated successfully, but these errors were encountered:
This is probably best as a plugin rather than a feature request, but I think Elder's architecture lends itself to something I have yet to see automatic, perfectly sized skeletons.
What I notice in my own process is that I put dummy data in while styling dynamic components, then I wire up the dynamic portion. Invariably I discover a few places wherein a store or reactive element fails during the static build and some workaround is needed. Then the rendered page has some empty bits that are never seen when live but are visible when javascript is disabled.
There are many solutions to this, but I think we could turn it into a big positive by adding a hook that replaces dummy elements with skeleton replacements. This could be done in a way that doesn't add any additional overhead -- usually, this requires one to specify the rendered size (which is hard to get right).
Any thoughts?
The text was updated successfully, but these errors were encountered: