Skip to content
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

fix: clean up VFragments when resetting component root #3360

Merged
merged 3 commits into from
Mar 1, 2023

Conversation

jye-sf
Copy link
Contributor

@jye-sf jye-sf commented Feb 23, 2023

Details

VFragments are not cleaned up properly when resetting component root because their .elm points to the end delimiter text node, not the root element.

Backport of #3363.

Does this pull request introduce a breaking change?

  • ✅ No, it does not introduce a breaking change.

Does this pull request introduce an observable change?

  • ⚠️ Yes, it does include an observable change.

GUS work item

@ravijayaramappa
Copy link
Contributor

ravijayaramappa commented Feb 23, 2023

unmount handles vfragment correctly. Reading the comments above resetComponentRoot, it does not want to call unmount for perf reasons. So, I suggest we can replicate that same special handling for VFragment in resetComponentRoot.

…3363)

* fix: add initial test case

* fix: recursively remove fragment children when resetting component root
@jye-sf jye-sf changed the title fix: @W-12593632 clean up VFragments when resetting component root fix: clean up VFragments when resetting component root Feb 24, 2023
jye-sf and others added 2 commits February 28, 2023 10:15
@jye-sf jye-sf marked this pull request as ready for review February 28, 2023 19:50
@jye-sf
Copy link
Contributor Author

jye-sf commented Mar 1, 2023

/nucleus ignore --reason "nucleus not testing backport against correct branch"

@jye-sf jye-sf merged commit 59c463f into spring23 Mar 1, 2023
@jye-sf jye-sf deleted the jye/fix-render-reset branch March 1, 2023 00:17
@salesforce-nucleus
Copy link
Contributor

❌ One or More Pre-release Checks Failed

  • ⚪️ Check PR user has rights to execute the workflow (skipped)
    Skipping PR owner check since PR has already been merged.

  • Check PR is approved
    PR 3360 is approved

  • ⚪️ Check PR is mergeable (skipped)
    PR 3360 has already been merged

  • ⚠️ Check GUS reference is present
    PR does not contain a reference to a GUS work item. You can update it any time by including '@W-XXXXXXX' into the title or body of the PR

  • Check no conflicting Github release
    A Github release already exists with a tag of v2.31.6. Please commit/push a version bump to the jye/fix-render-reset branch or have Nucleus do it for you by responding with the following comment
    /nucleus bump-version [version]

    To skip this check, run /nucleus release --force

  • Check NPM packages have not been released yet
    Version 2.31.6 of this project has already been published. If you would like to skip NPM publishing, then run /nucleus release --skipNpmRelease.If you want to bump the version in your source branch, run /nucleus bump-version [version]

  • ⚪️ Check Maven artifacts have not been released yet (skipped)
    Skipping check since project doesn't deliver Maven artifacts

  • ⚪️ Check GAV mapping exists for jar repo (skipped)
    Skipping GAV mapping check because a core jar is not being released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants