V2.0 Shell - Progressive Rendering with Skeleton#4138
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
e49a3b9 to
fcaac87
Compare
|
@PeerRich Done. Though this will introduce CLS. |
I see. maybe instead we wanna have the skeleton as the same size as the content? have one skeleton left for headline and one small one for the button on the right |
|
Yeah, that's some extra work just for the skeleton. By default, if no content is there in the element, it just collapses. We need a way to not have the element collapse. |
that's a good approach |
| @@ -51,7 +52,7 @@ interface CreateEventTypeBtnProps { | |||
| export default function CreateEventTypeButton(props: CreateEventTypeBtnProps) { | |||
| const { t } = useLocale(); | |||
There was a problem hiding this comment.
@hariombalhara why not use this instead?
| const { t } = useLocale(); | |
| const { t, isLocaleReady } = useLocale(); |
| export function useIsI18nLoading() { | ||
| const i18n = useViewerI18n(); | ||
| return i18n.status === "loading"; | ||
| } | ||
|
|
zomars
left a comment
There was a problem hiding this comment.
Removed isI18nLoading in favor of isLocaleReady, tested and it seems good to go. Thanks @hariombalhara please DM me if you feel this was a bad move.

What does this PR do?
Fixes # (issue)
Demo Loom
Also Fixes
Environment: Staging(main branch) / Production
Type of change
How should this be tested?
Checklist