Loading bar: use <CwaLoadingIndicator> in app.vue (cwa-nuxt-module#396)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nuxtjs
- Domain
- documentation, frontend
Research direction
Start with the docs pages that show the loading bar in app.vue and in layout examples, where CwaUiProgressBar appears. Replace the layout example with <CwaLoadingIndicator> placed above <NuxtLayout>, and note that it wraps <NuxtLoadingIndicator> and accepts its props. Add a short note on page:loading:end timing and on definePageMeta({ cwa: { disabled: true } }). Done means the examples and the prop/hook notes match the issue text.
Written by the indexing model from the issue text.
Description
cwa-nuxt-module#396 (1ed92548, unreleased after 2.0.0-alpha.15).
<CwaLoadingIndicator>is the recommended loading bar: put it inapp.vueabove<NuxtLayout>. It wraps<NuxtLoadingIndicator>and takes its props (color,height,throttle,duration, …); on CWA pages it shows the real page load percentage.CwaUiProgressBarin a layout is now optional; the template drops it.- Nuxt's
page:loading:end(and so the loading bar finishing and the scroll to top) now waits for the new CWA page to show. Pages withdefinePageMeta({ cwa: { disabled: true } })are never held. Anything an app hooks onpage:loading:endruns when the new page is on screen.
- Dominant language
- Vue
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from components-web-app/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#256 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#253 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
components-web-app/docs#255 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
components-web-app/docs#254 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
components-web-app/docs#237 · 2 comments ·
All issues in components-web-app/docs
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
AFLplusplus/AFLplusplus#2903 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
infrastructure qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
khuisman/mcp-gee-sweet#1068 ·
Maintainers usually reply within 1 day
-
documentation priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yeixio/toskar-core#697 ·
Maintainers usually reply within 1 day
-
area:ecosystem documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Chelis-Lang/chelis#3866 ·
Maintainers usually reply within 1 day