Live Reload is not working when you have a Child Component on the Parent Component
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- typescript
Rechercherichtung
No source files or tests are named. First reproduce the issue with a parent LWC containing a child LWC in the default namespace and inspect the live-reload error and local development server behavior. Done means edits to the parent or child component trigger a page reload and display the updated state.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
Live-reload is not working on a LWC which has another LWC as a Child Component. If so, the Page doesn't reload and an Error is thrown. I haven't checked if the Issue also occurs when you have a custom Namespace in your Org. We aren't using one and therefore I can only say that the Issue occurs with the default Namespace.
Steps To Reproduce:
- Create a new LWC with some basic Content
- Create another LWC with some basic Content and embed it in the Parent Component. (You need to use the default Namespace from Salesforce)
Expected Result
Live-reload is working also if you have one ore more Child Components on a LWC which uses the default Salesforce ("c") Namespace.
Actual Result
The Live-reload isn't happening and the previous State is still shown.
Additional Information
Screenshots:
Logs:
System Information
SF CLI:
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.67.7",
"nodeVersion": "node-v18.18.0",
"osVersion": "Windows_NT 10.0.22631",
"rootPath": "C:\\Users\\simon\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
"shell": "cmd.exe",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.8 (core)",
"@oclif/plugin-commands 4.1.8 (core)",
"@oclif/plugin-help 6.2.16 (core)",
"@oclif/plugin-not-found 3.2.25 (core)",
"@oclif/plugin-plugins 5.4.15 (core)",
"@oclif/plugin-search 1.2.14 (core)",
"@oclif/plugin-update 4.6.10 (core)",
"@oclif/plugin-version 2.2.15 (core)",
"@oclif/plugin-warn-if-update-available 3.1.21 (core)",
"@oclif/plugin-which 3.2.17 (core)",
"@salesforce/cli 2.67.7 (core)",
"@salesforce/lwc-dev-server 2.11.0 (user) published 1189 days ago (Wed Sep 08 2021)",
"apex 3.6.2 (core)",
"api 1.3.2 (core)",
"auth 3.6.73 (core)",
"data 3.11.3 (core)",
"deploy-retrieve 3.15.11 (core)",
"info 3.4.18 (core)",
"lightning-dev 1.3.0 (user) published 80 days ago (Fri Sep 20 2024) (latest is 1.9.4)",
"limits 3.3.39 (core)",
"marketplace 1.3.4 (core)",
"org 5.1.4 (core)",
"packaging 2.9.0 (core)",
"schema 3.3.40 (core)",
"settings 2.4.4 (core)",
"sobject 1.4.45 (core)",
"telemetry 3.6.20 (core)",
"templates 56.3.29 (core)",
"trust 3.7.41 (core)",
"user 3.6.2 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.2 (user) published 602 days ago (Mon Apr 17 2023) (latest is 1.2.1)",
"@salesforce/sfdx-scanner 3.16.0 (user) published 461 days ago (Tue Sep 05 2023) (latest is 4.7.0)",
"sfdx-git-delta 5.45.0 (user) published 81 days ago (Fri Sep 20 2024) (latest is 5.50.0)",
"sfdx-logs-delete 1.0.1 (user) published 882 days ago (Tue Jul 12 2022)"
]
}
OS:
Windows 11 Version 23H2
- Vorherrschende Sprache
- TypeScript
- Sterne
- 19
- Forks
- 19
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus salesforcecli/plugin-lightning-dev
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
salesforcecli/plugin-lightning-dev#686 · 1 Kommentar ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 42/100
salesforcecli/plugin-lightning-dev#627 · 2 Kommentare · 1 Reaktion ·
-
BUG P2
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 45/100
salesforcecli/plugin-lightning-dev#544 · 4 Kommentare ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 45/100
salesforcecli/plugin-lightning-dev#456 · 1 Reaktion ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
Alle Issues in salesforcecli/plugin-lightning-dev
Ähnliche Issues
-
awaiting-response bug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
wildcard/caro#1562 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 72/100
supadata-ai/mcp#27 ·
-
content
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
cosimochellini/one-piece-zero-spoiler#516 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
capricorn86/happy-dom#2485 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
lane: fast
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
unicef/adt-studio#946 ·
Maintainer antworten meist innerhalb von 2 Tagen